a give (ARM64 suport), and a question

[Jean-Baptiste-Lasselle]

Hello, congratulation for your work, first.

This issue:

• to give you modiications tested working for ARM64 support: https://github.com/3forges/packman/blob/feature/packer/full/appliances/lifecycle/oracle/post_install/kubernetes/k3d-metallb/meta-fuse-csi-plugin/ops.sh
• to ask a question: I think not, but is there a way I can do some dynamic volume provisioning using the pfnet-research/meta-fuse-csi-plugin CSI driver?

BR

[Jean-Baptiste-Lasselle]

ps: I don't use kind load, instead i use a local registry on host, that i connect to the kind docker network:

export KND_NET_NAME="decoderleco_knet"
export KND_NET_NAME="kind"
export KND_CLUSTER_NAME="k8-lab-decoderleco"
# docker network create ${KND_NET_NAME}

# 1. Create registry container unless it already exists
reg_name='kind-registry'
reg_port='5001'
if [ "$(docker inspect -f '{{.State.Running}}' "${reg_name}" 2>/dev/null || true)" != 'true' ]; then
  docker run \
    -d --restart=always -p "127.0.0.1:${reg_port}:5000" --network bridge --name "${reg_name}" \
    registry:2
fi

cat <<EOF | kind create cluster -n ${KND_CLUSTER_NAME} --wait 15m --config=-
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
containerdConfigPatches:
- |-
  [plugins."io.containerd.grpc.v1.cri".registry]
    config_path = "/etc/containerd/certs.d"
nodes:
- role: control-plane
- role: control-plane
- role: worker
- role: worker
# - role: worker
EOF

# Then we wait a bit to let the cluster get up'n running cosily
sleep 60s

kubectl cluster-info

# 3. Add the registry config to the nodes
#
# This is necessary because localhost resolves to loopback addresses that are
# network-namespace local.
# In other words: localhost in the container is not localhost on the host.
#
# We want a consistent name that works from both ends, so we tell containerd to
# alias localhost:${reg_port} to the registry container when pulling images
REGISTRY_DIR="/etc/containerd/certs.d/localhost:${reg_port}"
for node in $(kind get nodes -n ${KND_CLUSTER_NAME}); do
  docker exec "${node}" mkdir -p "${REGISTRY_DIR}"
  cat <<EOF | docker exec -i "${node}" cp /dev/stdin "${REGISTRY_DIR}/hosts.toml"
[host."http://${reg_name}:5000"]
EOF
done

# 4. Connect the registry to the cluster network if not already connected
# This allows kind to bootstrap the network but ensures they're on the same network
if [ "$(docker inspect -f='{{json .NetworkSettings.Networks.kind}}' "${reg_name}")" = 'null' ]; then
  docker network connect "kind" "${reg_name}"
fi

# 5. Document the local registry
# https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ConfigMap
metadata:
  name: local-registry-hosting
  namespace: kube-public
data:
  localRegistryHosting.v1: |
    host: "localhost:${reg_port}"
    help: "https://kind.sigs.k8s.io/docs/user/local-registry/"
EOF

[Jean-Baptiste-Lasselle]

pps: I just git pushed a cleanup of the ops.sh script