Skip to content

Disable insecure port#88

Merged
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
sttts:sttts-insecure-port
Apr 8, 2019
Merged

Disable insecure port#88
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
sttts:sttts-insecure-port

Conversation

@sttts
Copy link
Copy Markdown
Contributor

@sttts sttts commented Apr 4, 2019

@sttts
Copy link
Copy Markdown
Contributor Author

sttts commented Apr 4, 2019

/assign @s-urbaniak

@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 4, 2019
@sttts
Copy link
Copy Markdown
Contributor Author

sttts commented Apr 4, 2019

/assign @ravisantoshgudimetla

@sttts
Copy link
Copy Markdown
Contributor Author

sttts commented Apr 4, 2019

/hold

@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 Apr 4, 2019
@s-urbaniak
Copy link
Copy Markdown
Contributor

just a small request from my side, I enabled a tls based servicemonitor locally, but the kube-scheduler endpoints seem to point to the wrong port:

$ kubectl -n openshift-kube-scheduler get ep scheduler -o yaml
apiVersion: v1
kind: Endpoints
metadata:
...
  ports:
  - name: https
    port: 8443
    protocol: TCP

I believe these should rather be 10259. Is it possible to fix this in conjunction with this change?

s-urbaniak added a commit to s-urbaniak/cluster-monitoring-operator that referenced this pull request Apr 5, 2019
s-urbaniak added a commit to s-urbaniak/cluster-monitoring-operator that referenced this pull request Apr 5, 2019
@sttts sttts force-pushed the sttts-insecure-port branch from 0c838c1 to ed4a0c7 Compare April 5, 2019 07:27
@s-urbaniak
Copy link
Copy Markdown
Contributor

/lgtm
I guess we'll have some chicken and egg integration woes here in conjunction with cluster monitoring, but this should be resolved once openshift/cluster-monitoring-operator#308 and this PR both are merged.

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

@s-urbaniak s-urbaniak left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: s-urbaniak, sttts

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

@sttts
Copy link
Copy Markdown
Contributor Author

sttts commented Apr 8, 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 Apr 8, 2019
@openshift-merge-robot openshift-merge-robot merged commit 0e400bc into openshift:master Apr 8, 2019
s-urbaniak added a commit to s-urbaniak/cluster-monitoring-operator that referenced this pull request Apr 8, 2019
In accordance to
openshift/cluster-kube-scheduler-operator#88
we can now enable TLS for the kube scheduler.
s-urbaniak added a commit to s-urbaniak/cluster-monitoring-operator that referenced this pull request Apr 10, 2019
s-urbaniak added a commit to s-urbaniak/installer that referenced this pull request Apr 10, 2019
Recently, the control plane switched to secure ports in [1] and [2].
This aligns them in the installer.

[1]
openshift/cluster-kube-scheduler-operator#88
[2]
openshift/cluster-kube-controller-manager-operator#207
s-urbaniak added a commit to s-urbaniak/cluster-monitoring-operator that referenced this pull request Apr 12, 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.

5 participants