Skip to content
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

Merged

Commits on Oct 12, 2017

  1. Configuration menu
    Copy the full SHA
    3b88b4a View commit details
    Browse the repository at this point in the history
  2. UPSTREAM: 53037: Verify client cert before reusing existing bootstrap

    The cert may have expired.
    smarterclayton committed Oct 12, 2017
    Configuration menu
    Copy the full SHA
    e7de2fd View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    79750e9 View commit details
    Browse the repository at this point in the history
  4. 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.
    smarterclayton committed Oct 12, 2017
    Configuration menu
    Copy the full SHA
    1b2f999 View commit details
    Browse the repository at this point in the history
  5. 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.
    smarterclayton committed Oct 12, 2017
    Configuration menu
    Copy the full SHA
    ae01595 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    13ef9b9 View commit details
    Browse the repository at this point in the history
  7. Set a default certificate duration for bootstrapping

    CFSSL throws an opaque error, and bootstrapping requires user
    intervention to configure anyway.
    smarterclayton committed Oct 12, 2017
    Configuration menu
    Copy the full SHA
    737d65b View commit details
    Browse the repository at this point in the history
  8. 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
    smarterclayton committed Oct 12, 2017
    Configuration menu
    Copy the full SHA
    a04e494 View commit details
    Browse the repository at this point in the history
  9. 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.
    smarterclayton committed Oct 12, 2017
    Configuration menu
    Copy the full SHA
    c9db154 View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    c3d5830 View commit details
    Browse the repository at this point in the history
  11. 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.
    smarterclayton committed Oct 12, 2017
    Configuration menu
    Copy the full SHA
    ae05ccd View commit details
    Browse the repository at this point in the history