Skip to content
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

deploy_k8s fails due to missing kubernetes_master_port on AWS #271

Closed
seanknox opened this issue Feb 26, 2018 · 6 comments
Closed

deploy_k8s fails due to missing kubernetes_master_port on AWS #271

seanknox opened this issue Feb 26, 2018 · 6 comments
Assignees
Labels

Comments

@seanknox
Copy link

@seanknox seanknox commented Feb 26, 2018

using v0.14.0:

STR:

EXPECTED:

  • CFCR is deployed

ACTUAL:

  • fails due to missing kubernetes_master_port in director.yml
Task 13 | 05:57:56 | Preparing deployment: Preparing deployment (00:00:03)
Task 13 | 05:58:02 | Error: Unable to render instance groups for deployment. Errors are:
  - Unable to render jobs for instance group 'master'. Errors are:
    - Unable to render templates for job 'kube-apiserver'. Errors are:
      - Failed to find variable '/seano_kubo-bosh/seano-bosho-cluster/kubernetes_master_port' from config server: HTTP Code '404', Error: 'The request could not be completed because the credential does not exist or you do not have sufficient authorization.'

I couldn't find any scripts that sed'ed kubernetes_master_port as with other variables in director.yml, so I manually set it to 443 and reran, which worked.

@cf-gitbot
Copy link

@cf-gitbot cf-gitbot commented Feb 26, 2018

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/155504547

The labels on this github issue will be updated when the story is started.

@akshaymankar
Copy link
Contributor

@akshaymankar akshaymankar commented Feb 26, 2018

Hi @seanknox, thanks for reporting the bug. We'll prioritise and work on it.

Although, I think you should've set the port to 8443, but the fact that 443 worked for you makes me question if it is even used anymore.

@seanknox
Copy link
Author

@seanknox seanknox commented Feb 26, 2018

I thought 8443 was the right one, glad to have confirmation of that. :)

@iainsproat
Copy link
Contributor

@iainsproat iainsproat commented Mar 13, 2018

Hi @seanknox

Just to let you know that we've proposed a solution to your issue and are awaiting PM input before proceeding.

@sharms
Copy link

@sharms sharms commented Mar 23, 2018

Release 0.15.0 sets this to 8443 by default if blank, have you given that a try?

@glestaris
Copy link
Contributor

@glestaris glestaris commented Apr 25, 2018

Fixed in 50ccfd6 and docs were updated in cloudfoundry/docs-cfcr@003a324. Closing this.

@glestaris glestaris closed this Apr 25, 2018
lubronzhan pushed a commit to pivotal-cf/pks-kubo-deployment that referenced this issue Apr 18, 2019
* Bump k8s binaries to 1.12.2

[#161377281]

Signed-off-by: Travis Hall <thall@vmware.com>

* Template kube-controller-manager certificates

- This commit introduces a new job property `tls.kube-controller-manager`

[#161377281]

Signed-off-by: Travis Hall <thall@vmware.com>

* Upload blobs and add their IDs

[#161377281]

Signed-off-by: Urvashi Reddy <ureddy@pivotal.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants