Open ellistarn opened 1 year ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
Would also be great to have a suite to run core against. Notice we also ended up just copy pasting some of the AWS E2E Suites and changing the nodeclass to be AKSNodeclass. https://github.com/Azure/karpenter-provider-azure/tree/main/test/suites We ported over Integration, drift, nodeclaim and utilization. Running consolidation, chaos, etc is a next goal, but would be interesting to see if there is a space for the two teams to share one test matrix that can run on both providers when developing against core for some tests that work the same minus nodeclass on providers.
This would be a major step forward as upstream CAS has no Azure Conformance tests(We are looking to add some in near future).
Would be great to make sure that for new core versions it will not cause regressions for other cloud providers. Given we do some of this testing when importing core so not sure on the priority.
CC: @jackfrancis who is doing gods work of adding conformance tests for azure for CAS I believe.
I can open a separate issue for this if thats desired to not take the conversation away from the scheduler conformance tests. Just figured its tangentially related to getting core e2es setup for the scheduler conformance.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
Tell us about your request What do you want us to build?
I would be great to verify our scheduler conformance by running upstream scheduler conformance tests.
Community Note