Create cloudrc contents in openstack-config-secret #432
+18
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We are currently only creating the `clouds.yaml` and `secure.yaml` for the openstack client and not the classic `cloudrc` file that was usually sourced for individual clients. This makes sense if there were parity between the openstck client and all the individual clients, but there are still missing features. For example: - The `openstack volume service list` cannot show the cluster. - The `openstack volume service list` cannot show the backend state. - There is no support for any of the default volume type commands: set, show, list, unset. These are some of the ones we know about, but there could be more. Users will need to use the old `cinder` client, so we should make it convenient for them by having the `cloudrc` available in the `openstackclient` pod. This patch adds the `cloudrc` key in the `openstack-config-secret` secret to make it possible for the `openstack-operator` to mount it in the `openstackclient` pod.
Akrog
added a commit
to Akrog/openstack-operator
that referenced
this pull request
Jun 27, 2024
We are currently only creating the `clouds.yaml` and `secure.yaml` in the `openstackclient` pod, and that is enough for the openstack client, but unfortunately this is not enough since there is no parity between that client and the individual clients. For example it is missing (though it has upstream patches in progress): - The `openstack volume service list` cannot show the cluster. - The `openstack volume service list` cannot show the backend state. - There is no support for any of the default volume type commands: set, show, list, unset. These are some of the ones we know about, but there could still be some other missing. Users will need to use the old `cinder` client, so we should make it convenient for them by having the `cloudrc` available in the `openstackclient` pod. Depends-On: openstack-k8s-operators/keystone-operator#432
Akrog
added a commit
to Akrog/openstack-operator
that referenced
this pull request
Jun 28, 2024
We are currently only creating the `clouds.yaml` and `secure.yaml` in the `openstackclient` pod, and that is enough for the openstack client, but unfortunately this is not enough since there is no parity between that client and the individual clients. For example it is missing (though it has upstream patches in progress): - The `openstack volume service list` cannot show the cluster. - The `openstack volume service list` cannot show the backend state. - There is no support for any of the default volume type commands: set, show, list, unset. These are some of the ones we know about, but there could still be some other missing. Users will need to use the old `cinder` client, so we should make it convenient for them by having the `cloudrc` available in the `openstackclient` pod. Depends-On: openstack-k8s-operators/keystone-operator#432
|
@frenzyfriday can you please approve this? It's needed for openstack-k8s-operators/openstack-operator#890 |
|
/assign @frenzyfriday |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Akrog, ASBishop, stuggi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
vakwetu
pushed a commit
to vakwetu/openstack-operator
that referenced
this pull request
Sep 12, 2024
We are currently only creating the `clouds.yaml` and `secure.yaml` in the `openstackclient` pod, and that is enough for the openstack client, but unfortunately this is not enough since there is no parity between that client and the individual clients. For example it is missing (though it has upstream patches in progress): - The `openstack volume service list` cannot show the cluster. - The `openstack volume service list` cannot show the backend state. - There is no support for any of the default volume type commands: set, show, list, unset. These are some of the ones we know about, but there could still be some other missing. Users will need to use the old `cinder` client, so we should make it convenient for them by having the `cloudrc` available in the `openstackclient` pod. Depends-On: openstack-k8s-operators/keystone-operator#432
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are currently only creating the
clouds.yamlandsecure.yamlfor the openstack client and not the classiccloudrcfile that was usually sourced for individual clients.This makes sense if there were parity between the openstck client and all the individual clients, but there are still missing features. For example:
openstack volume service listcannot show the cluster.openstack volume service listcannot show the backend state.These are some of the ones we know about, but there could be more.
Users will need to use the old
cinderclient, so we should make it convenient for them by having thecloudrcavailable in theopenstackclientpod.This patch adds the
cloudrckey in theopenstack-config-secretsecret to make it possible for theopenstack-operatorto mount it in theopenstackclientpod.