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

Linode provider with Arkade ingress-nginx - label too long #140

Closed
JLCode-tech opened this issue Aug 25, 2021 · 2 comments
Closed

Linode provider with Arkade ingress-nginx - label too long #140

JLCode-tech opened this issue Aug 25, 2021 · 2 comments

Comments

@JLCode-tech
Copy link

Following this how to link:
https://docs.inlets.dev/#/get-started/quickstart-ingresscontroller-cert-manager?id=install-nginx-ingress

Running into this error using arkade install nginx-ingress :
2021/08/24 21:41:53 Provisioning started with provider: linode host: ingress-nginx-controller-tunnel │
│ E0824 21:41:54.292104 1 controller.go:326] error syncing 'default/ingress-nginx-controller-tunnel': [400] [label] Length must be 3-32 characters, requeuing

Expected Behaviour

linode smartscript created and linode server created.

Current Behaviour

2021/08/24 21:41:53 Provisioning started with provider: linode host: ingress-nginx-controller-tunnel │
│ E0824 21:41:54.292104 1 controller.go:326] error syncing 'default/ingress-nginx-controller-tunnel': [400] [label] Length must be 3-32 characters, requeuing

These errors from the operator container log

Possible Solution

Reduce the label appending

Steps to Reproduce (for bugs)

Following this guide:
https://docs.inlets.dev/#/get-started/quickstart-ingresscontroller-cert-manager?id=install-nginx-ingress

Your Environment

K3s deployed with K3sup, script below:
#!/bin/bash
set -e

CH=latest

echo Installing Pi4
k3sup install --user jarrodl --ssh-key /home/jarrodl/.ssh --ip 192.168.1.250 --k3s-channel $CH --cluster --k3s-extra-args '--no-deploy traefik --no-deploy servicelb --write-kubeconfig-mode 644'

  • inlets-operator version, find via kubectl get deploy inlets-operator -o wide
    jarrodl@jabba:~$ kubectl get deploy inlets-operator -o wide
    NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
    inlets-operator 1/1 1 1 11h inlets-operator ghcr.io/inlets/inlets-operator:0.14.1 app.kubernetes.io/instance=inlets-operator,app.kubernetes.io/name=inlets-operator

  • Kubernetes distribution i.e. minikube v0.29.0., KinD v0.5.1, Docker Desktop: K3s

  • Kubernetes version kubectl version:
    jarrodl@jabba:~$ kubectl version
    Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4+k3s1", GitCommit:"3e250fdbab72d88f7e6aae57446023a0567ffc97", GitTreeState:"clean", BuildDate:"2021-08-19T19:10:03Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/arm64"}

  • Operating System and version (e.g. Linux, Windows, MacOS): Linux Ubuntu 20.10

  • Cloud provisioner: linode

@dirien
Copy link
Contributor

dirien commented Aug 25, 2021

@alexellis
Copy link
Member

I've fixed cloud-provision#17 and when we have this vendored back into the operator, the scenario above will work, and any names > 32 characters will fail early without creating and executing the startup script.

Thanks for the input here.

Alex

alexellis added a commit that referenced this issue Sep 15, 2021
Ref: #140

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
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

3 participants