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

Installation of provider-helm fails with "resource name may not be empty" in air-gapped environment. #201

Closed
emreyokur opened this issue Oct 11, 2023 · 1 comment

Comments

@emreyokur
Copy link

We have an air-gapped kubernetes environment.
We followed the installation procedure of crossplane and successfully installed it. However, when we want to install provider-helm, we see the following error in the output of "kubectl describe provider".

_Warning UnpackPackage 10m (x24 over 28m) packages/provider.pkg.crossplane.io cannot unpack package: failed to fetch package digest from remote: resource name may not be empty_

Since we have an air-gapped environment, we did some manipulations which none worked.

  • We pulled provider-helm-controller image and pushed it to our internal private registry.
  • We forked the provider-helm repository on github. Modified crossplane.yaml, added spec.controller.image which points to our internal image registry which I have mentioned.
  • We run the pipeline (i.e build provider-helm from scratch - we pushed the resulting image to our personal docker.hub account, then pulled from there and installed it to our internal private registry.)
  • Finally, we applied the below yaml to install provider-helm, however the error message did not change.
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-helm
spec:
  package: <our_private_image_registry>/crossplane-contrib/provider-helm:master
  packagePullPolicy: Always
  packagePullSecrets:
    - name: <our_pull_secret>

PS: We have internal registry but we do not use self-signed certificate. We use Digicert Global.

Any clue or help is appreciated.

@emreyokur
Copy link
Author

We have solved our issue.
Provider's PackagePullSecrets seems ok, but in the values file of crossplane, we noticed that we made an syntax error. When we fixed it, provider installed successfully. Though, we did not expect that the provider uses crossplane's imagePullSecret, and that made us troubleshoot the issue a bit difficult.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant