Known issues for 1.0.0-beta

[deviantony]

This is a thread to reference known issues for the 1.0.0-beta release.

• Unable to list Secret and ConfigMap resources with k9s: Known issues for 1.0.0-beta #68 (comment)
• An error is raised when creating a namespace with Lens/OpenLens: Known issues for 1.0.0-beta #68 (comment)
• Creating workloads and resources inside a non existing namespace silently fails: Known issues for 1.0.0-beta #68 (comment)
• Applying a manifest that creates a namespace and multiple resources within that namespace will fail with "namespace not found" error: Known issues for 1.0.0-beta #68 (comment)
• Creating services when k2d runs under Podman fails: Known issues for 1.0.0-beta #68 (comment)

[deviantony]

Unable to list Secret and ConfigMap resources using k9s: derailed/k9s#2238

The following errors are returned.

For secrets:

ERR Watcher failed for v1/secrets -- no kind "SecretList" is registered for version "v1" in scheme "pkg/runtime/scheme.go:100"

For configmaps:

ERR Watcher failed for v1/configmaps -- no kind "ConfigMapList" is registered for version "v1" in scheme "pkg/runtime/scheme.go:100"

[deviantony]

• Fixed via fix: introduce required properties for lens namespace creation #69

An error is raised when creating a namespace with Lens/OpenLens.

The following error is displayed:

However, refreshing the view shows that the namespace is actually created:

[deviantony]

• Fixed via feat: added namespace validation to prevent unwanted operations to pr… #70

Creating workloads and resources inside a non existing namespace silently fails.

# kubectl outputs a success deployment
kubectl create deployment nginx --image=nginx:latest -n doesntexist
deployment.apps/nginx created

The following error is raised in k2d logs:

2023-10-05T07:39:58.300Z        ERROR   controller/controller.go:190    unable to create deployment     {"error": "Error response from daemon: network k2d-doesntexist not found"}

On a vanilla k8s, the following error is returned by kubectl:

kubectl create deployment nginx --image=nginx:latest -n doesntexist
error: failed to create deployment: namespaces "doesntexist" not found

[deviantony]

• Fixed via fix: update namespace creation and deletion logic #72

Applying a manifest that creates a namespace and multiple resources within that namespace will fail with "namespace not found" error:

Using the following nodered.yml manifest:

apiVersion: v1
kind: Namespace
metadata:
  name: node-red
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: node-red
  namespace: node-red
  labels:
    app: node-red
spec:
  selector:
    matchLabels:
      app: node-red
  template:
    metadata:
      labels:
        app: node-red
    spec:
      containers:
      - name: node-red
        image: nodered/node-red:latest
        ports:
        - containerPort: 1880
        securityContext:
          privileged: true
        volumeMounts:
        - name: node-red-data
          mountPath: /data
        env:
        - name: NODE_NAME
          valueFrom:
            fieldRef:
              fieldPath: spec.nodeName
        - name: TZ
          value: America/Los_Angeles
      volumes:
      - name: node-red-data
        persistentVolumeClaim:
          claimName: node-red-claim
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: node-red-claim
  namespace: node-red
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
---
apiVersion: v1
kind: Service
metadata:
  name: node-red
  namespace: node-red
spec:
  selector:
    app: node-red
  type: LoadBalancer
  ports:
    - name: node-red-ui
      port: 1880
      protocol: TCP
      targetPort: 1880

Trying to apply this manifest:

kubectl apply -f nodered.yml
namespace/node-red created
Error from server (NotFound): error when creating "nodered.yml": namespaces "node-red" not found
Error from server (NotFound): error when creating "nodered.yml": namespaces "node-red" not found
Error from server (NotFound): error when creating "nodered.yml": namespaces "node-red" not found

Likely, the deletion of the manifest will fail as well:

kubectl delete -f nodered.yml
namespace/node-red created
Error from server (NotFound): error when creating "nodered.yml": namespaces "node-red" not found
Error from server (NotFound): error when creating "nodered.yml": namespaces "node-red" not found
Error from server (NotFound): error when creating "nodered.yml": namespaces "node-red" not found

This issue has been introduced following the fix for #68 (comment) (via #70)

[deviantony]

• After more testing, this seems to happen only on "unusual" Podman setups/configurations such as installing Podman on Ubuntu. The recommendation here is to use Podman on CentOS 8 which works without issue. We recommend this approach unless you know what you are doing when installing Podman on a non standard OS/configuration.

Applying a manifest that contains a service definition when running k2d under Podman fails to create the container with the following error:

ERROR	controller/controller.go:212	unable to update container	{"error": "unable to create container: Error response from daemon: fill out specgen: ulimit option \"RLIMIT_NOFILE=1048576:1048576\" requires name=SOFT:HARD, failed to be parsed: invalid ulimit type: RLIMIT_NOFILE", "request_id": "04b0d175-ce7b-4384-93dc-139f9d1fc132"}

[deviantony]

Closing in favor of #83