cluster-api-provider-azure icon indicating copy to clipboard operation
cluster-api-provider-azure copied to clipboard

Add e2e tests for private endpoints

Open nawazkh opened this issue 8 months ago • 2 comments

/kind feature

Describe the solution you'd like [A clear and concise description of what you want to happen.]

  • With https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/4108 landing very soon, we would like to have an e2e test scenario added to test the private endpoint service in CAPZ.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

  • cluster-api-provider-azure version: n/a
  • Kubernetes version: (use kubectl version): n/a
  • OS (e.g. from /etc/os-release): n/a

nawazkh avatar Dec 05 '23 00:12 nawazkh

For context, the tricky part here is determining what the private endpoint in the test can link to. In my testing I've been spinning up an ACR instance (with the premium SKU) and linking to that, but I'm not sure if there's a cheaper option.

nojnhuh avatar Dec 08 '23 17:12 nojnhuh

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Mar 07 '24 18:03 k8s-triage-robot

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Apr 06 '24 18:04 k8s-triage-robot