Skip to content

Disable gateway ingress in am-pattern-2 default values#150

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/disable-gateway-ingress
Draft

Disable gateway ingress in am-pattern-2 default values#150
Copilot wants to merge 2 commits intomainfrom
copilot/disable-gateway-ingress

Conversation

Copy link
Contributor

Copilot AI commented Feb 26, 2026

Purpose

Disable gateway ingress in the am-pattern-2-all-in-one_GW deployment pattern documentation.

Goals

Set kubernetes.ingress.gateway.enabled to false in the pattern-2 default values file.

Approach

Changed line 155 in docs/am-pattern-2-all-in-one_GW/default_values.yaml:

kubernetes:
  ingress:
    gateway:
-     enabled: true
+     enabled: false

User stories

N/A - Documentation configuration update

Release note

Gateway ingress disabled by default in am-pattern-2-all-in-one_GW default values

Documentation

N/A - This change updates the documentation itself

Training

N/A

Certification

N/A - Configuration default change only

Marketing

N/A

Automation tests

  • Unit tests: N/A - Documentation file change
  • Integration tests: N/A - Documentation file change

Security checks

Samples

N/A

Related PRs

N/A

Migrations (if applicable)

N/A

Test environment

N/A - Documentation change only

Learning

N/A


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Co-authored-by: kavindasr <59206135+kavindasr@users.noreply.github.com>
Copilot AI changed the title [WIP] Disable gateway ingress in configuration Disable gateway ingress in am-pattern-2 default values Feb 26, 2026
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.

3 participants