Skip to content

ci: [Service Tags] add public ips with service tags for LBs during cluster creation #3277

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

Merged
merged 68 commits into from
Apr 8, 2025

Conversation

k-routhu
Copy link
Contributor

@k-routhu k-routhu commented Dec 18, 2024

Reason for Change:

Adding service tags to all public ips. This change adds public ips and attaches these ips as load balancer outbound ips during cluster creation. Branch spathak/add-service-tags is where all the changes were made and tested -- created this branch based off of that one.

Testing:

  • All testing was done on branch spathak/add-service-tags
  • We had a couple of PRs out by Esteban and Shubham to update service tags. However, all of the PRs targeted hack/aks/Makefile, so I went ahead and made all of the updates in this branch.
  • Also added ipv6 public ips to load balancer outbound ips for dualstack clusters to resolve errors

Tested changes in a couple of Cilium pipelines:

Cilium Nightly Pipeline
The public ips created have service tags attached to them, and the ips fall within the allowed ranges for the locations they were created. E2E tests are failing in this run and in master too, so failures aren't bc of these changes.

CNI Release Test
All of the public ips created have service tags attached to them, and the ips fall within the allowed ranges for the locations they were created

CNI - LSG Integration Test
The clusters get created here successfully with the correct public ips. The integration tests do fail, but I checked with John Payne -- he mentioned that the integration tests fail frequently because they're heavily dependent on a partner team (Canonical). He suggested running Cilium Private Test pipelines on v1.14 and v1.16 (the next two on the list) and the remaining pipelines with the service tags. The remaining pipelines look good and create public ips as expected, so I believe we should be good to go on that front.

ACN PR Pipeline
All of the public ips created have service tags attached to them, and the ips fall within the allowed ranges for the locations they were created

@k-routhu k-routhu added this pull request to the merge queue Mar 19, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 20, 2025
Copy link

This pull request is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale due to inactivity. label Mar 27, 2025
Copy link

github-actions bot commented Apr 3, 2025

Pull request closed due to inactivity.

@github-actions github-actions bot closed this Apr 3, 2025
@github-actions github-actions bot deleted the krouthu/service-tag branch April 3, 2025 00:01
@k-routhu k-routhu restored the krouthu/service-tag branch April 3, 2025 19:11
@k-routhu
Copy link
Contributor Author

k-routhu commented Apr 3, 2025

reopening PR

@k-routhu k-routhu reopened this Apr 3, 2025
@k-routhu k-routhu dismissed stale reviews from rbtr and jpayne3506 via 22e90d4 April 3, 2025 19:14
@github-actions github-actions bot removed the stale Stale due to inactivity. label Apr 4, 2025
@k-routhu k-routhu requested a review from rbtr April 7, 2025 20:04
@k-routhu k-routhu enabled auto-merge April 7, 2025 20:38
@k-routhu k-routhu added this pull request to the merge queue Apr 7, 2025
Merged via the queue into master with commit 3a1fb2b Apr 8, 2025
96 checks passed
@k-routhu k-routhu deleted the krouthu/service-tag branch April 8, 2025 00:47
@jpayne3506 jpayne3506 added release/1.4 Change affects v1.4 release train needs-backport Change needs to be backported to previous release trains release/1.5 Change affects v1.5 release train labels May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Infra or tooling. needs-backport Change needs to be backported to previous release trains release/1.4 Change affects v1.4 release train release/1.5 Change affects v1.5 release train
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants