Skip to content

Conversation

@Miciah
Copy link
Contributor

@Miciah Miciah commented May 9, 2019

Use LoadBalancerService as the default endpoint publishing strategy type on Azure.

This commit is related to NE-185.

  • operator/v1/types_ingress.go (IngressControllerSpec): Document that the default endpoint publishing strategy type on Azure is LoadBalancerService.
  • operator/v1/zz_generated.swagger_doc_generated.go: Regenerate.

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 9, 2019
@Miciah Miciah force-pushed the NE-185-operator-slash-ingress-default-Azure-to-LoadBalancerService branch 2 times, most recently from b815670 to e08cf0c Compare May 14, 2019 20:12
@Miciah Miciah changed the title operator/ingress: Default Azure to LoadBalancer operator/ingress: Default Azure and GCP to LoadBalancer May 14, 2019
@Miciah Miciah changed the title operator/ingress: Default Azure and GCP to LoadBalancer operator/ingress: Default Azure to LoadBalancer May 14, 2019
@Miciah Miciah force-pushed the NE-185-operator-slash-ingress-default-Azure-to-LoadBalancerService branch from e08cf0c to b815670 Compare May 14, 2019 20:14
Use LoadBalancerService as the default endpoint publishing strategy type on
Azure.

This commit is related to NE-185.

https://jira.coreos.com/browse/NE-185

* operator/v1/types_ingress.go (IngressControllerSpec): Document that the
default endpoint publishing strategy type on Azure is LoadBalancerService.
* operator/v1/zz_generated.swagger_doc_generated.go: Regenerate.
@Miciah Miciah force-pushed the NE-185-operator-slash-ingress-default-Azure-to-LoadBalancerService branch from b815670 to d73d5fb Compare May 14, 2019 20:20
@ironcladlou
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 15, 2019
@ironcladlou
Copy link
Contributor

cc @smarterclayton for approval

@smarterclayton
Copy link
Contributor

/lgtm
/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ironcladlou, Miciah, smarterclayton

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 May 16, 2019
@soltysh
Copy link
Contributor

soltysh commented May 16, 2019

/hold
we need to create release-4.1 first

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 16, 2019
@soltysh
Copy link
Contributor

soltysh commented May 17, 2019

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 17, 2019
@openshift-merge-robot openshift-merge-robot merged commit 94e0b39 into openshift:master May 17, 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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants