-
Notifications
You must be signed in to change notification settings - Fork 237
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
Kind 0.8.1 devenv #978
Kind 0.8.1 devenv #978
Conversation
Script seems to work once I made two Fedora 32 hacks to fix docker container networking in general:
So this script replaces both of our current ones for kind and registry into one much smaller and simpler script. Next step podman. |
hive-operator appears to be successful, but hotloops and pins the cpu. Investigating. |
Hotloop fixed, details in commit, some interesting complications may be coming with Kube 1.18+ due to server side apply. Updated docs. |
``` | ||
|
||
Create a kind cluster named 'hive' to deploy to. You can create as many kind clusters as you need.: | ||
Create a local insecure registry (if one does not already exist) and then a kind cluster named 'hive' to deploy to. You can create as many kind clusters as you need and you have sufficient RAM. | ||
|
||
```bash | ||
./hack/create-kind-cluster.sh hive |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a note after this that the following error is expected the first time this is run and is not indicative of an error.
Error response from daemon: container fcca36a26da5601d6453c0c53ab5909eb6ca8ffe42de0f8634dd7213f107cef0 is not connected to network kind
hack/create-kind-cluster.sh
Outdated
" | ||
EOF | ||
fi | ||
# tell https://tilt.dev to use the registry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this section required? If so, we should remove the references to tilt.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't even realize, no it does not seem necessary, removing.
docs/developing.md
Outdated
``` | ||
|
||
Create a kind cluster named 'hive' to deploy to. You can create as many kind clusters as you need.: | ||
Create a local insecure registry (if one does not already exist) and then a kind cluster named 'hive' to deploy to. You can create as many kind clusters as you need and you have sufficient RAM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The part about sufficient RAM could use some grammatical work. I do not think that it is necessary to call out specifically RAM.
Create a local insecure registry (if one does not already exist) and then a kind cluster named 'hive' to deploy to. You can create as many kind clusters as you need and you have sufficient RAM. | |
Create a local insecure registry (if one does not already exist) and then a kind cluster named 'hive' to deploy to. You can create multiple kind clusters. Each kind cluster needs a unique name, which is specified by the argument passed to the script. |
Switch to a much simpler script for creating a kind cluster to develop hive against, with an integrated registry. The registry is now linked to the container with docker networking and the new script takes place of both of the old ones, if there is no registry container one will be started for you.
1.18 introduces beta of server side apply, which adds field tracking to object metadata for who set the value of a field. On Update, this includes a timestamp. Hive operator was blindly doing updates and thus the timestamp was constantly changing, leading to a hotloop.
Updates pushed and WIP removed. Matthew and Joel have confirmed this works for them so I think we're ok to proceed. Added some additional notes on the Fedora hacks that may be required. |
Needs approval, should be ready to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bah, had one very minor comment that I never submitted from a week ago. Otherwise, this looks good to me.
docs/developing.md
Outdated
|
||
Create a kind cluster named 'hive' to deploy to. You can create as many kind clusters as you need.: | ||
Create a local insecure registry (if one does not already exist) and then a kind cluster named 'hive' to deploy to. You can create additional clusters if desired by provising a different name argument to the script. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/provising/providing/
|
||
```bash | ||
export KUBECONFIG="$(kind get kubeconfig-path --name="hive")" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new kind does not have get kubeconfig-path
so also need to change the docs in Adopting clusterdeployments section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I replaced it with /path/to/admin/kubeconfig.
PR updated, would love to get merged before freeze! |
docs/developing.md
Outdated
@@ -130,7 +129,7 @@ To create a kind cluster and adopt: | |||
|
|||
```bash | |||
./hack/create-kind-cluster.sh cluster1 | |||
bin/hiveutil create-cluster --base-domain=new-installer.openshift.com kind-cluster1 --adopt --adopt-admin-kubeconfig=$(kind get kubeconfig-path --name="cluster1") --adopt-infra-id=fakeinfra --adopt-cluster-id=fakeid | |||
bin/hiveutil create-cluster --base-domain=new-installer.openshift.com kind-cluster1 --adopt --adopt-admin-kubeconfig=/path/to/cluster/admin/kubeconfig get kubeconfig-path --name="cluster1") --adopt-infra-id=fakeinfra --adopt-cluster-id=fakeid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove the following.
get kubeconfig-path --name="cluster1")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arghhh sorry, updated again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgoodwin, staebler The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
New script is based off an example in kind.
Been trying to get this to work but it's stuck communicating with the insecure registry, no route to host despite supposedly being on the network. I've exec'd into the kind control plane container and using curl, neither localhost, nor the container name (kind-registry), nor the ip seem to work. It just can't reach that container.
Any advice welcome, going to keep trying to poke at this.
Still haven't tried it with podman.
Fixes: #833