[WIP] OCPEDGE-649: check if CCMO present#3999
Conversation
|
@qJkee: This pull request references OCPVE-628 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: qJkee The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/hold until openshift/api#1579 gets merged |
|
Is this work expected to merge in 4.15 or right now it is mainly a POC? Right now linked card is epic, please link it to a story with details so that we can understand what exactly we need to review. Also, as per PR description, it seems like it will require qe testing because we are skipping passing kubelet flags. |
|
@qJkee: This pull request references OCPEDGE-649 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@qJkee: This pull request references OCPEDGE-649 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
cdoern
left a comment
There was a problem hiding this comment.
I don't think we can safely merge a PR with a replaced API. Also some general comments about comments, errors etc.
| sigs.k8s.io/yaml v1.3.0 // indirect | ||
| ) | ||
|
|
||
| replace github.com/openshift/api => github.com/qjkee/api v0.0.0-20231024160705-d90a3dcdd9ec |
There was a problem hiding this comment.
I don't think we can ship with a replace in the go.mod
There was a problem hiding this comment.
It's just for using api objects.
Once I get this approved/lgtm I'll merge my branch to the upstream(openshift/api) and then just bump regular openshift/api version.
See openshift/api#1579 (comment)
There was a problem hiding this comment.
This is going to conflict with: #4012 which we want to get in first for TRT. So i advise we hold off on this one until the API bump from the linked PR gets in.
|
Thanks all for reviewing the PR! Putting hold for QE pre-merge testing. |
|
@sinnykumari |
There was a problem hiding this comment.
As long as comments are added and the errors are more fatal I can get behind this. However, I do not think we can merge this because it'll wreak havoc against: #4012 I see what Joel is saying about merging and agreeing on the dependencies first. However, merging this will make it impossible for the above PR to merge since the API code I am using will not include this custom API code.
|
Overall this looks fine, also as per #3999 (comment) , respective QE team is already testing this functionality. Major missing item is getting openshift/api#1579 merged and adapting this PR to switch back to using openshit/api |
cdoern
left a comment
There was a problem hiding this comment.
I think I found what is breaking the unit tests, PTAL
| version: "" | ||
| type: "" | ||
| replicas: 3 | ||
| kind: ConfigMap |
There was a problem hiding this comment.
This is the configmap causing the error in the bootstrap_unit test logs that says bootstrap_test.go:432: Unknown object type *v1.ConfigMap
| @@ -0,0 +1,49 @@ | |||
| apiVersion: v1 | |||
There was a problem hiding this comment.
do we need this? it seems to be breaking bootstrap tests
|
/retest |
|
/test unit |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
Add check if CCMO is present within the cluster. If not, then do not pass the flag --cloud-provider to the kubelet
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
@qJkee: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Add check if CCMO is present within the cluster. If not, then do not pass the flag to kubelet related to the cloud providers
Here I try to read the install config from the cluster or from the disc and detect enabled capabilities.
If CloudController capability is disabled(
cloud controller manager operatoris not installed to the cluster) we return an empty value passed to the--cloud-providerkubelet flag. We passexternalonly in case if cloud provider is actuallyexternalto support manual installation of providers