Skip to content

Use an internal ingress by default when the cluster is marked internal - #2538

Merged
openshift-merge-robot merged 2 commits into
openshift:masterfrom
ironcladlou:private-ingress-controller
Oct 23, 2019
Merged

Use an internal ingress by default when the cluster is marked internal#2538
openshift-merge-robot merged 2 commits into
openshift:masterfrom
ironcladlou:private-ingress-controller

Conversation

@ironcladlou

Copy link
Copy Markdown
Contributor

When the cluster is internal according to the install config's publishing field,
render an internal default ingresscontroller so that ingress remains consistent
with the intent for the entire cluster to be "internal".

This commit is part of the "User-defined Default Ingress Controller" enhancement
proposal[1] and implements the final user-facing component of the feature.

[1] https://github.com/openshift/enhancements/blob/master/enhancements/user-defined-default-ingress-controller.md

@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Oct 21, 2019
@ironcladlou

Copy link
Copy Markdown
Contributor Author

/cc @abhinavdahiya

@ironcladlou

Copy link
Copy Markdown
Contributor Author

/cc @mwoodson

Comment thread pkg/asset/manifests/ingress.go Outdated
@ironcladlou
ironcladlou force-pushed the private-ingress-controller branch 2 times, most recently from dc7f5e0 to fa89cf0 Compare October 21, 2019 21:39
@ironcladlou

Copy link
Copy Markdown
Contributor Author

/retest

@ironcladlou

Copy link
Copy Markdown
Contributor Author

@abhinavdahiya

I managed to test this on AWS using upi/aws/cloudformation/01_vpc.yaml to set up the VPC/subnets and then specifying publish: Internal in the install config. I ran the installer build from a bastion host within the VPC and came out the other side with a functional cluster with ingress using a load balancer with scope: Internal. Everything seems to be fine.

Hope that's a sufficient test. I can provide more details if necessary!

@ironcladlou

Copy link
Copy Markdown
Contributor Author

All feedback addressed and verified with a manual test, PTAL.

When the cluster is internal according to the install config's publishing field,
render an internal default ingresscontroller so that ingress remains consistent
with the intent for the entire cluster to be "internal".

This commit is part of the "User-defined Default Ingress Controller" enhancement
proposal[1] and implements the final user-facing component of the feature.

[1] https://github.com/openshift/enhancements/blob/master/enhancements/user-defined-default-ingress-controller.md
@ironcladlou
ironcladlou force-pushed the private-ingress-controller branch from fa89cf0 to e47fd39 Compare October 22, 2019 10:43
@ironcladlou

Copy link
Copy Markdown
Contributor Author

Rebased.

@abhinavdahiya

Copy link
Copy Markdown
Contributor

@abhinavdahiya

I managed to test this on AWS using upi/aws/cloudformation/01_vpc.yaml to set up the VPC/subnets and then specifying publish: Internal in the install config. I ran the installer build from a bastion host within the VPC and came out the other side with a functional cluster with ingress using a load balancer with scope: Internal. Everything seems to be fine.

Hope that's a sufficient test. I can provide more details if necessary!

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 22, 2019
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, ironcladlou

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 22, 2019
@openshift-bot

Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@ironcladlou

Copy link
Copy Markdown
Contributor Author

/retest

@openshift-bot

Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot

Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
openshift-merge-robot merged commit 1c32be0 into openshift:master Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants