The existing manifest was not updated, we need to wait for a new
rrelease but until then, it is better we host it ourselves so the guide
works correctly.
In addition, remove a comment that no longer applies since current
configuration of Ingress uses only standard options.
In addition to the extraPortMapping example, document how to run the
Ingress with a LoadBalancer provisioning by cloud-provider kind, that
provides a more realistic experience.
It also removes the specific implimentation details of the guide so it
is more agnostic of the Ingress implementation.
Change-Id: I865e72ca4571f0c513a1e9e412bc5e9c06a67a51
* doc: remove copy button background colour
the motivation for this commit is that I often get a feeling of having
marked the COPY buttons, but when I check, it turns out I haven't
that happens because the COPY buttons have a background colour that is
basically the same as when you mark text
* doc: use emoji for copy button
kind seems to be fond of emojis, it can maybe work here as well?
* doc: copy kubernetes.io code blocks design
as per feedback in PR
* doc: comply with copycode.svg license
* Revert "doc: comply with copycode.svg license"
This reverts commit c018fda4bc.
The latest metallb version is configurable via CRs instead of configmap.
Here we suggest using the latest version and we change the configuration
from configmap to CRs.
Signed-off-by: Federico Paolinelli <fedepaol@gmail.com>
The example script for creating a kind cluster with a local registry
will connect the container to the "kind" network. The first time the
local registry is created, this is fine and is what is needed. On
subsequent runs to create new clusters, if the local registry container
has already been set up, the command to attach to the "kind" network
will emit an error message to the create output that can be confusing.
This updates the example script to do a basic check of the registry
containers network configuration. If the kind network appears to be
already connected, then the script will not attempt to connect it again.
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
As per the kubeadm KEP for "master" label/taint changes:
- kubeadm 1.24 nodes will only have the "control-plane" label.
- kubeadm 1.24 nodes will have both the "master"
and "control-plane" taints.
- kubeadm 1.25 nodes will have only the "control-plane" taint
Adapt kind to these changes and add TODOs with links
for the tracking issue in k-sigs/kind.
kind-registry is accessed from inside docker, so
regardless of what port is used when starting it with:
-p "127.0.0.1:${reg_port}:5000"
It must always be accessed as kind-registry:5000 and not
kind-registry:${reg_port}
Docker for mac fails with the following if --publish is set to 127.0.0.0:
> bind: can't assign requested address.
Updating the example to be working out of the box.
