-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Align service config generation #64
Comments
gibizer
added a commit
to gibizer/placement-operator
that referenced
this issue
Dec 7, 2023
This did not removed the root usage from the init container. We should get rid of the init container instead. (See openstack-k8s-operators#64) Implements: https://issues.redhat.com/browse/OSPRH-1374
gibizer
added a commit
to gibizer/placement-operator
that referenced
this issue
Dec 7, 2023
This did not removed the root usage from the init container. We should get rid of the init container instead. (See openstack-k8s-operators#64) Implements: https://issues.redhat.com/browse/OSPRH-1374
gibizer
added a commit
to gibizer/placement-operator
that referenced
this issue
Dec 7, 2023
This did not removed the root usage from the init container. We should get rid of the init container instead. (See openstack-k8s-operators#64) Implements: https://issues.redhat.com/browse/OSPRH-1374
openshift-merge-bot bot
pushed a commit
that referenced
this issue
Dec 8, 2023
This did not removed the root usage from the init container. We should get rid of the init container instead. (See #64) Implements: https://issues.redhat.com/browse/OSPRH-1374
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently placement-operator generates the service config into a ConfigMap and uses an init container and ENV vars to add passwords to the config. To align with other operators we need to:
The text was updated successfully, but these errors were encountered: