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

authorizationWebhookConfigFile field not recognized #7386

Closed
apolovov opened this issue Aug 7, 2019 · 5 comments
Closed

authorizationWebhookConfigFile field not recognized #7386

apolovov opened this issue Aug 7, 2019 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@apolovov
Copy link

apolovov commented Aug 7, 2019

1. What kops version are you running?
Version 1.14.0-alpha.3 (git-cd430998f)

2. What Kubernetes version are you running?
1.15.1

3. What cloud provider are you using?
gce

7. Please provide your cluster manifest.

apiVersion: kops/v1alpha2
kind: Cluster
metadata:
  creationTimestamp: 2019-07-20T19:47:06Z
  generation: 1
  name: polovov-sandbox-13.k8s.local
spec:
  api:
    loadBalancer:
      type: Public
  authorization:
    rbac: {}
  channel: stable
  cloudProvider: gce
  configBase: gs://polovov-sandbox/polovov-sandbox-13.local
  docker:
    logDriver: ""
    version: 17.03.2
  etcdClusters:
  - etcdMembers:
    - instanceGroup: master-europe-west4-a
      name: a
    name: main
  - etcdMembers:
    - instanceGroup: master-europe-west4-a
      name: a
    name: events
  fileAssets:
  - content: |
      ...
    name: authorization-webhook
    path: /srv/kubernetes/assets/authorization-webhook.yaml
  iam:
    allowContainerRegistry: true
    legacy: false
  kubeAPIServer:
    authorizationMode: Webhook,RBAC
    authorizationWebhookConfigFile: /srv/kubernetes/assets/authorization-webhook.yaml
    featureGates:
      PodShareProcessNamespace: "true"
    runtimeConfig:
      batch/v2alpha1: "true"
  kubeControllerManager:
    featureGates:
      PodShareProcessNamespace: "true"
  kubeScheduler:
    featureGates:
      PodShareProcessNamespace: "true"
  kubelet:
    anonymousAuth: false
    featureGates:
      PodShareProcessNamespace: "true"
  kubernetesApiAccess:
  - 0.0.0.0/0
  kubernetesVersion: 1.15.1
  masterInternalName: api.polovov-sandbox-13.k8s.local
  masterPublicName: api.polovov-sandbox-13.k8s.local
  networking:
    kubenet: {}
  nonMasqueradeCIDR: 100.64.0.0/10
  project: flant-sandbox
  sshAccess:
  - 0.0.0.0/0
  subnets:
  - name: europe-west4
    region: europe-west4
    type: Public
  topology:
    dns:
      type: Public
    masters: public
    nodes: public

I tried to add Webhook authorization mechanism to my existing cluster by configuring .spec.kubeAPIServer.authorizationMode and .spec.kubeAPIServer.authorizationWebhookConfigFile, but only authorizationMode option works and authorizationWebhookConfigFile is not recognized.

I think this issue is related to #7321 and #7344.

@anderseknert
Copy link
Contributor

@driusha 1.14.0-alpha.3 predates the PR with that fix. Should work with 1.14.0-beta.1 and above.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 1, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 31, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants