Skip to content
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

fix: install GatewayClass separately as a shared resource for all namespaces #360

Conversation

leninmehedy
Copy link
Member

@leninmehedy leninmehedy commented Sep 19, 2023

Description

This pull request changes the following:

  • install FST gateway class separately as a shared resource for all namespaces
  • The setup script execution is made idempotent

Related Issues

@leninmehedy leninmehedy linked an issue Sep 19, 2023 that may be closed by this pull request
@leninmehedy leninmehedy changed the title fix: install FST gateway class separately as a shared resource for all namespaces fix: install GatewayClass separately as a shared resource for all namespaces Sep 19, 2023
@github-actions
Copy link

Unit Test Results

16 files  ±0  16 suites  ±0   29s ⏱️ -9s
85 tests ±0  82 ✔️ ±0  3 💤 ±0  0 ±0 
86 runs  ±0  83 ✔️ ±0  3 💤 ±0  0 ±0 

Results for commit d365e52. ± Comparison against base commit 6d1c0a5.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@@ -0,0 +1,9 @@
apiVersion: gateway.networking.k8s.io/v1beta1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should move this to a separate helm chart and not hide it in the dev tools. This will be necessary for all cluster deployments including automatic cluster setup my the infrastructure library.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I am working on another branch that was created from this branch. I'll convert into a separate chart and update the setup script and values.yaml accordingly as a separate PR to avoid conflicts.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created a ticket #361

@leninmehedy
Copy link
Member Author

This is superseded by: #363

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants