-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Feat: Upgrade external OCI cloud controller manager #11378
base: master
Are you sure you want to change the base?
Feat: Upgrade external OCI cloud controller manager #11378
Conversation
f095ad4
to
466ec5c
Compare
/ok-to-test |
Thanks @tico88612 The release note maybe /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tico88612, yankay 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 |
/lgtm |
/retest-required |
466ec5c
to
a94fb0f
Compare
New changes are detected. LGTM label has been removed. |
a94fb0f
to
3d71a93
Compare
@VannTen, Could you help me with this PR? I want to remove the |
Hum, OCI is somewhat ambiguous name ... is there a way to use which denotes clearly this is the oracle cloud infra controller ? I know the previous internal was named OCI, but since we're creating a new one anyway, maybe we could have a less confusing name ? (-> confusion with open container image) For the content itself: Thanks |
OCI is an awkward acronym; it conflicts with the Open Container Initiative, and I don't have a better idea now. Some of the code was migrated from
Previously, the variables |
OCI is an awkward acronym; it conflicts with the Open Container Initiative, and I don't have a better idea now.
Maybe oracle_oci ?
Or oracle_cloud(_infra) ?
> For the content itself:
> I've seen several check of the form : var is defined and var == something -> can we have the var in defaults instead or is there some things preventing that ?
Previously, the variables `cloud_provider` and `external_cloud_provider` were defined before executing the associated tasks. I was under the impression that there were anti-dumbing checks.
I meant more stuf list `oci_security_lists or `external_oci_auth_user`
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not that you can use the assert module for all these checks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean like this?
- name: "External OCI Cloud Controller Manager | Credentials Check | external_oci_auth_key"
ansible.builtin.assert:
that:
- not oci_use_instance_principals
- external_oci_auth_key is not defined or not external_oci_auth_key
fail_msg: "external_oci_auth_key is missing"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, if the check are not conditional, maybe you can add all put them in one assert ? (since it accepts multiples statement).
We still get the assert in the error message, I figure it's as good as "is missing" wdty ?
3d71a93
to
6610267
Compare
I think giving a default value to the user setting is unnecessary because it's not a required option in Kubespray, and it's only triggered if |
It's not only about defaults, it's also about documentation. One of the goals is to use roles/defaults/*.yml as documentation ultimately, rather than the sample inventory.
It also makes templates more readable (IMO) to not have the double checks (is defined + testing the value)
|
What do you mean? Do other user settings go to |
Yes, they should.
|
Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
6610267
to
b58a8ef
Compare
Wouldn't adding the user setting eliminate the need for |
Well if the default value ("" for most of them FWICS) is acceptable no need to test for it. On the other hand if it isn't you still need to assert.
|
What type of PR is this?
/kind feature
What this PR does / why we need it:
roles/kubernetes-app/cloud-provider
.role/kubernetes-app/external_cloud_controller
.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: