-
Notifications
You must be signed in to change notification settings - Fork 35
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
Reconcile CAPC Cluster as CloudStack CKS Cluster (Default: Opt Out) #350
Reconcile CAPC Cluster as CloudStack CKS Cluster (Default: Opt Out) #350
Conversation
Skipping CI for Draft Pull Request. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-cloudstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Currently - in progress, draft - not fit or ready for review yet. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #350 +/- ##
==========================================
+ Coverage 25.66% 25.80% +0.13%
==========================================
Files 59 62 +3
Lines 5563 4906 -657
==========================================
- Hits 1428 1266 -162
+ Misses 3996 3508 -488
+ Partials 139 132 -7 ☔ View full report in Codecov by Sentry. |
/run-e2e -c 4.19 |
@vishesh92 Invalid command: /run-e2e -c 4.19
The command to run e2e test for CAPC. Usage: /run-e2e [-k Kubernetes_Version] [-c CloudStack_Version] [-h Hypervisor] [-i Template/Image] [-f Kubernetes_Version_Upgrade_From] [-t Kubernetes_Version_Upgrade_To]
Examples:
|
/run-e2e -c 4.18 |
@vishesh92 a jenkins job has been kicked to run test with following paramaters:
|
/run-e2e -c 4.19 |
@vishesh92 a jenkins job has been kicked to run test with following paramaters:
|
Test Results : (tid-495)
|
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.
/lgtm
Thanks a lot!
I see you are trying to run tests. Let me know when you are done and ready to merge and I'll approve
Test Results : (tid-496)
|
Thanks @g-gaston for review. @kiranchavala is currently testing this PR. Once he gives a go ahead, we can merge this PR. Meanwhile, I will fix the conflicts in go.mod. |
/lgtm |
@rohityadavcloud: you cannot LGTM your own PR. In 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-sigs/prow repository. |
@vishesh92 while I opened the PR, it’s largely your work. Pl feel free to resubmit a new PR or lgtm this when this is ready after QA. cc @kiranchavala |
/run-e2e -c 4.19 |
@rohityadavcloud a jenkins job has been kicked to run test with following paramaters:
|
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.
@kiranchavala can you add a /approve |
Test Results : (tid-497)
|
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.
/lgtm
@kiranchavala: changing LGTM is restricted to collaborators In 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kiranchavala, rohityadavcloud, weizhouapache 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 |
Issue #, if available:
#310
Description of changes:
The notion of a CAPC cluster represents a k8s cluster created and managed by CAPC. While a similar construct exists in CloudStack in form of CKS (CloudStack K8S Service) cluster. This PR aims to address #310 by introducing logic that can reconcile a CAPC cluster to a CKS cluster, while having this feature disabled by default (i.e. opt out by default). This will be useful for users (and integrations) who want to be aware about a potentially externally managed K8S cluster in CloudStack via the reconciled CKS cluster.
ACS 4.19 and later support such reconciliation with introduction of feature support PRs in upstream CloudStack releases:
apache/cloudstack-go#59
apache/cloudstack#7515
apache/cloudstack-documentation#315
Previously attempted as #250
Testing performed:
To be updated
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.