-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Allow bootstrap configuration to be configured and reentrant #16571
Allow bootstrap configuration to be configured and reentrant #16571
Commits on Oct 12, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 3b88b4a - Browse repository at this point
Copy the full SHA 3b88b4aView commit details -
UPSTREAM: 53037: Verify client cert before reusing existing bootstrap
The cert may have expired.
Configuration menu - View commit details
-
Copy full SHA for e7de2fd - Browse repository at this point
Copy the full SHA e7de2fdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 79750e9 - Browse repository at this point
Copy the full SHA 79750e9View commit details -
Tolerate being unable to remove /var/run/openshift-sdn
When we mount /var/run/openshift-sdn into the container, we need to be able to clear its contents but the directory itself cannot be removed as it is a mount point. Also clarify one error.
Configuration menu - View commit details
-
Copy full SHA for 1b2f999 - Browse repository at this point
Copy the full SHA 1b2f999View commit details -
The proxy health server should be on, it does not leak info
This makes running in a separate process for networks able to have a health check and for metrics to be reported.
Configuration menu - View commit details
-
Copy full SHA for ae01595 - Browse repository at this point
Copy the full SHA ae01595View commit details -
Configuration menu - View commit details
-
Copy full SHA for 13ef9b9 - Browse repository at this point
Copy the full SHA 13ef9b9View commit details -
Set a default certificate duration for bootstrapping
CFSSL throws an opaque error, and bootstrapping requires user intervention to configure anyway.
Configuration menu - View commit details
-
Copy full SHA for 737d65b - Browse repository at this point
Copy the full SHA 737d65bView commit details -
Add --bootstrap-config-name to kubelet
This allows the kubelet to be configured to load default configuration out of a known namespace. By default it is openshift-node/node-config. Correct an error in bootstrapping where errors weren't logged, and properly ignore forbidden errors when trying to load the config map. Add a better description of bootstrapping to openshift start node. Ensure the volume directory is correctly loaded from node-config during bootstrapping instead of being overwritten into the config directory. Enable client and server rotation on the node automatically when bootstrapping, and only do a client certificate creation (server bootstrapping done by kubelet only). This unfortunately requires setting a fake value in the node config that will be cleared later - as we are moving towards a future where node-config does not exist this entire section will likely go away. Relax validation on node-config to allow cert-dir to be provided instead of explicit certificates. bootstrap
Configuration menu - View commit details
-
Copy full SHA for a04e494 - Browse repository at this point
Copy the full SHA a04e494View commit details -
Auto-create openshift-node and given nodes read on node-config
Other config variants will be stored in this location. The new namespace ensures clean security isolation.
Configuration menu - View commit details
-
Copy full SHA for c9db154 - Browse repository at this point
Copy the full SHA c9db154View commit details -
Configuration menu - View commit details
-
Copy full SHA for c3d5830 - Browse repository at this point
Copy the full SHA c3d5830View commit details -
Ensure openshift start network can run in a pod
Need to be able to take node-config from bootstrap node. For openshift start network the --kubeconfig flag from the CLI overrides the value of masterKubeConfig in the provided node config. If the value is empty (like it is by default) the in-cluster-config is used. Reorganize the node startup slightly so there is even less overlap between kubelet and network. A future change will completely separate these two initialization paths.
Configuration menu - View commit details
-
Copy full SHA for ae05ccd - Browse repository at this point
Copy the full SHA ae05ccdView commit details