CKS: skip default egress policy check for vpc network offerings#11998
CKS: skip default egress policy check for vpc network offerings#11998shwstppr merged 2 commits intoapache:4.22apache/cloudstack:4.22from weizhouapache:4.22-fix-cks-vpc-networkweizhouapache/cloudstack:4.22-fix-cks-vpc-networkCopy head branch name to clipboard
Conversation
|
@blueorangutan package |
|
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.22 #11998 +/- ##
=========================================
Coverage 17.56% 17.56%
+ Complexity 15546 15545 -1
=========================================
Files 5910 5910
Lines 529125 529125
Branches 64628 64628
=========================================
+ Hits 92934 92939 +5
+ Misses 425737 425733 -4
+ Partials 10454 10453 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15648 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-14774)
|
|
@blueorangutan package |
|
@kiranchavala a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 16548 |
kiranchavala
left a comment
There was a problem hiding this comment.
LGTM
-
Create a VPC network and tier with ACL ( allow all)
-
Launch a cks cluster in the vpc network
-
CKS cluster launched successfully
-
Launch a nginx deployment on the cks cluster
-
Nginx deployment launched fine
|
Merging based on tests and review |
…he#11998) This PR fixes apache#11995 Steps to reproduce the issue - create a vpc - create a vpc tier with default offering `DefaultIsolatedNetworkOfferingForVpcNetworks` - register CKS ISO - create CKS on the vpc tier expected: succeed actual: failed with error `Kubernetes service has not been configured properly to provision Kubernetes clusters`
Description
This PR fixes #11995
Steps to reproduce the issue
DefaultIsolatedNetworkOfferingForVpcNetworksexpected: succeed
actual: failed with error
Kubernetes service has not been configured properly to provision Kubernetes clustersTypes of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?