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

Knative deployments failing in EKS and AKS #4668

Open
vfarcic opened this issue Jul 10, 2019 · 0 comments

Comments

@vfarcic
Copy link
Contributor

commented Jul 10, 2019

Summary

When using Knative deployments, ksvc cannot pull images from ECR in AKS and EKS (it works in GKE).

Steps to reproduce the behavior

Create a cluster in AKS (or EKS).

jx edit deploy \
    --team \
    --kind knative \
    --batch-mode

jx create quickstart \
    --language go \
    --project-name jx-knative \
    --batch-mode

STAGING_NAMESPACE=[...] # Raplace with the staging Namespace

kubectl -n $STAGING_NAMESPACE get ksvc

The output of the last command:

NAME         DOMAIN                                        LATESTCREATED      LATESTREADY   READY   REASON
jx-knative   jx-knative.cd-staging.40.121.183.151.nip.io   jx-knative-bpxdz                 False   RevisionMissing
kubectl -n $STAGING_NAMESPACE describe ksvc jx-knative

The output:

Name:         jx-knative
Namespace:    cd-staging
Labels:       chart=jx-knative-0.0.2
              jenkins.io/chart-release=jx
              jenkins.io/version=3
Annotations:  jenkins.io/chart: env
              kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"serving.knative.dev/v1alpha1","kind":"Service","metadata":{"annotations":{"jenkins.io/chart":"env"},"labels":{"chart":"jx-k...
              serving.knative.dev/creator: system:serviceaccount:cd:tekton-bot
              serving.knative.dev/lastModifier: system:serviceaccount:cd:tekton-bot
API Version:  serving.knative.dev/v1alpha1
Kind:         Service
Metadata:
  Creation Timestamp:  2019-07-10T18:40:12Z
  Generation:          1
  Resource Version:    7810
  Self Link:           /apis/serving.knative.dev/v1alpha1/namespaces/cd-staging/services/jx-knative
  UID:                 26f90bd5-a342-11e9-b39e-e6d24a31cca1
Spec:
  Run Latest:
    Configuration:
      Revision Template:
        Metadata:
          Creation Timestamp:  <nil>
        Spec:
          Container:
            Image:              jxrocks.azurecr.io/vfarcic/jx-knative:0.0.2
            Image Pull Policy:  IfNotPresent
            Liveness Probe:
              Http Get:
                Path:                 /
                Port:                 0
              Initial Delay Seconds:  60
              Period Seconds:         10
              Success Threshold:      1
              Timeout Seconds:        1
            Name:                     
            Readiness Probe:
              Http Get:
                Path:             /
                Port:             0
              Period Seconds:     10
              Success Threshold:  1
              Timeout Seconds:    1
            Resources:
              Limits:
                Cpu:     100m
                Memory:  256Mi
              Requests:
                Cpu:        80m
                Memory:     128Mi
          Timeout Seconds:  300
Status:
  Conditions:
    Last Transition Time:        2019-07-10T18:40:13Z
    Message:                     Revision "jx-knative-bpxdz" failed with message: Unable to fetch image "jxrocks.azurecr.io/vfarcic/jx-knative:0.0.2": unsupported status code 401; body: .
    Reason:                      RevisionFailed
    Status:                      False
    Type:                        ConfigurationsReady
    Last Transition Time:        2019-07-10T18:40:13Z
    Message:                     Configuration "jx-knative" does not have any ready Revision.
    Reason:                      RevisionMissing
    Status:                      False
    Type:                        Ready
    Last Transition Time:        2019-07-10T18:40:13Z
    Message:                     Configuration "jx-knative" does not have any ready Revision.
    Reason:                      RevisionMissing
    Status:                      False
    Type:                        RoutesReady
  Domain:                        jx-knative.cd-staging.40.121.183.151.nip.io
  Latest Created Revision Name:  jx-knative-bpxdz
  Observed Generation:           1
Events:
  Type    Reason   Age                    From                Message
  ----    ------   ----                   ----                -------
  Normal  Created  9m25s                  service-controller  Created Configuration "jx-knative"
  Normal  Created  9m24s                  service-controller  Created Route "jx-knative"
  Normal  Updated  9m24s (x4 over 9m24s)  service-controller  Updated Service "jx-knative"

A similar result is observable from EKS as well.

Expected behavior

ksvc can pull the image.

Actual behavior

ksvc can NOT pull the image.

Jx version

The output of jx version is:

NAME               VERSION
jx                 2.0.441
jenkins x platform 2.0.768
Kubernetes cluster v1.12.8
kubectl            v1.14.3
helm client        Client: v2.14.1+g5270352
git                git version 2.20.1 (Apple Git-117)
Operating System   Mac OS X 10.14.5 build 18F203

Jenkins type

  • Serverless Jenkins X Pipelines (Tekton + Prow)
  • Classic Jenkins

Kubernetes cluster

AKS or EKS

Operating system / Environment

macOS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.