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

control maestro server istio ingress restriction via helm value #624

Merged
merged 1 commit into from
Sep 23, 2024

Conversation

geoberle
Copy link
Collaborator

What this PR does

for the CS integration environment, we require the maestro istio policy to not restrict ingress sources because the source namespace name is dynamically generated during CS PR checks.

the RESTRICT_ISTIO_INGRESS var controls if ingress is restricted from the well known CS namespace in prod, or not restricted at all

Jira:
Link to demo recording:

Special notes for your reviewer

for the CS integration environment, we require the maestro istio policy to not restrict ingress sources because the source namespace name is dynamically generated during CS PR checks.

the RESTRICT_ISTIO_INGRESS var controls if ingress is restricted from the well known CS namespace in prod, or not restricted at all

Signed-off-by: Gerd Oberlechner <[email protected]>
@mjlshen mjlshen merged commit acd8887 into main Sep 23, 2024
21 checks passed
@mjlshen mjlshen deleted the cs-sandbox-istio branch September 23, 2024 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants