Skip to content

[WIP] OSDOCS-14578: adds ingress control options to MicroShift #95759

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ShaunaDiaz
Copy link
Contributor

@ShaunaDiaz ShaunaDiaz commented Jul 8, 2025

Version(s):
4.20+

Issue:
OSDOCS-14578

Link to docs preview:
Default MicroShift config.yaml values
Ingress control config procedure

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 8, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 8, 2025

@ShaunaDiaz: This pull request references OSDOCS-14578 which is a valid jira issue.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 8, 2025
@ShaunaDiaz ShaunaDiaz added this to the Planned for 4.20 GA milestone Jul 8, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 8, 2025

@ShaunaDiaz: This pull request references OSDOCS-14578 which is a valid jira issue.

In response to this:

Version(s):
4.20+

Issue:
OSDOCS-14578

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 8, 2025

@ShaunaDiaz: This pull request references OSDOCS-14578 which is a valid jira issue.

In response to this:

Version(s):
4.20+

Issue:
OSDOCS-14578

Link to docs preview:
Default MicroShift config.yaml values

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 8, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 9, 2025

@ShaunaDiaz: This pull request references OSDOCS-14578 which is a valid jira issue.

In response to this:

Version(s):
4.20+

Issue:
OSDOCS-14578

Link to docs preview:
Default MicroShift config.yaml values
Ingress control config procedure

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@ShaunaDiaz ShaunaDiaz force-pushed the OSDOCS-14578 branch 3 times, most recently from baa9403 to c76cd57 Compare July 9, 2025 15:38
|Specifies whether the field name of the cookie exactly matches the capture cookie setting or is a prefix of the capture cookie setting. Valid values are `Exact` for an exact string match and `Prefix` for a string prefix match.

* If the `Exact` setting is used, a name must also be specified in the `httpCaptureCookiesname` field.
* If the `Prefix` setting is used, a prefix must be specified in the `httpCaptureCookiesnamePrefix` field. For example, specifying matchType "Prefix" and namePrefix "foo" will capture a cookie named "foo" or "foobar" but not one named "bar". The first matching cookie is captured.
Copy link
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] RedHat.Spacing: Keep one space between words in 'field. For'. For more information, see RedHat.Spacing.

Copy link

openshift-ci bot commented Jul 9, 2025

@ShaunaDiaz: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.20 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants