yes i didn't know about that!! Now, when creating a new cluster at GCP, the Legacy Authorization is disabled but default. So when I enabled it. I was able to implement my old configurations with no issues. thanks for your link, I will look into that and try to test it.
On Friday, May 18, 2018 at 9:34:14 PM UTC-4, Ahmet Alp Balkan wrote: > > I recommend just following the tutorial at > https://cloud.google.com/community/tutorials/nginx-ingress-gke to install > nginx-ingress on GKE. > > It goes through both RBAC enabled and disabled instructions. > > On Fri, May 18, 2018 at 3:06 PM Montassar Dridi <montass...@gmail.com > <javascript:>> wrote: > >> Hello >> >> I'm using google kubenretes engine. My cluster node version is 1.7. Since >> that version became unsupported by Google cloud for creating new cluster, I >> need to use 1.8 or 1.9. >> I'm having issues implimenting my nginx-ingress-controller yaml file at >> the new versioned cluster but I keep getting this error : >> >> Using build: https://github.com/bprashanth/contrib.git - >> git-92b2bac when using >> gcr.io/google_containers/nginx-ingress-controller:0.8.3 >> >> and this error hen using quay.io/kubernetes-ingress-controller/nginx- >> ingress-controller:0.9.0 >> >> It seems the cluster it is running with Authorization enabled >> (like RBAC) and there is no permissions for the ingress controller. Please >> check the configuration >> >> here is my my nginx-ingress-controller file >> >> apiVersion: v1 >> kind: Service >> metadata: >> name: default-http-backend >> labels: >> k8s-app: default-http-backend >> spec: >> ports: >> - port: 80 >> targetPort: 8080 >> protocol: TCP >> name: http >> selector: >> k8s-app: default-http-backend >> --- >> apiVersion: v1 >> kind: ReplicationController >> metadata: >> name: default-http-backend >> spec: >> replicas: 1 >> selector: >> k8s-app: default-http-backend >> template: >> metadata: >> labels: >> k8s-app: default-http-backend >> spec: >> terminationGracePeriodSeconds: 60 >> containers: >> - name: default-http-backend >> # Any image is permissable as long as: >> # 1. It serves a 404 page at / >> # 2. It serves 200 on a /healthz endpoint >> image: gcr.io/google_containers/defaultbackend:1.0 >> livenessProbe: >> httpGet: >> path: /healthz >> port: 8080 >> scheme: HTTP >> initialDelaySeconds: 30 >> timeoutSeconds: 5 >> ports: >> - containerPort: 8080 >> resources: >> limits: >> cpu: 10m >> memory: 20Mi >> requests: >> cpu: 10m >> memory: 20Mi >> --- >> apiVersion: v1 >> kind: ReplicationController >> metadata: >> name: nginx-ingress-controller >> labels: >> k8s-app: nginx-ingress-lb >> spec: >> replicas: 1 >> selector: >> k8s-app: nginx-ingress-lb >> template: >> metadata: >> labels: >> k8s-app: nginx-ingress-lb >> name: nginx-ingress-lb >> spec: >> terminationGracePeriodSeconds: 60 >> containers: >> - image: gcr.io/google_containers/nginx-ingress-controller:0.8.3 >> name: nginx-ingress-lb >> imagePullPolicy: Always >> readinessProbe: >> httpGet: >> path: /healthz >> port: 10254 >> scheme: HTTP >> livenessProbe: >> httpGet: >> path: /healthz >> port: 10254 >> scheme: HTTP >> initialDelaySeconds: 10 >> timeoutSeconds: 1 >> # use downward API >> env: >> - name: POD_NAME >> valueFrom: >> fieldRef: >> fieldPath: metadata.name >> - name: POD_NAMESPACE >> valueFrom: >> fieldRef: >> fieldPath: metadata.namespace >> ports: >> - containerPort: 80 >> hostPort: 80 >> - containerPort: 443 >> hostPort: 443 >> # we expose 18080 to access nginx stats in url /nginx-status >> # this is optional >> - containerPort: 18080 >> hostPort: 18080 >> args: >> - /nginx-ingress-controller >> - --default-backend-service=$(POD_NAMESPACE)/default-http-backend >> - --nginx-configmap=$(POD_NAMESPACE)/nginx-ingress-cfg >> - --watch-namespace=production >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Kubernetes user discussion and Q&A" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to kubernetes-use...@googlegroups.com <javascript:>. >> To post to this group, send email to kubernet...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/kubernetes-users. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
