Conversation
|
aos-ci-test |
f6b17c7 to
a59a356
Compare
|
aos-ci-test |
453e5c6 to
dcdc2c7
Compare
f4c4291 to
3fc903b
Compare
3fc903b to
cb14a7a
Compare
|
/retest |
32cd654 to
ff05261
Compare
|
/retest |
ff05261 to
e1142cf
Compare
|
/retest |
2c7a78b to
0e43e4e
Compare
|
@michaelgugino @sdodson, @smarterclayton |
eed1e73 to
8d3ac16
Compare
6c787e1 to
73bf47f
Compare
73bf47f to
ab59305
Compare
|
|
||
| openshift_master_node_config_networkconfig_mtu: 1450 | ||
|
|
||
| openshift_master_node_config_kubeletargs_cpu: 500m |
There was a problem hiding this comment.
These seem like node group specific settings, applied as defaults to a node-config generated per node group.
ab59305 to
6bf2d71
Compare
6bf2d71 to
47d2e20
Compare
|
I don't want to block this PR any longer. We definitely need to plan follow up work though. |
|
Yeah, this can continue in subsequent PRs. I have GCE bootstrapping and I'm close to a PR that turns it on for origin's conformance_gce suite, which will stepping stone to doing a full image build -> cluster turn up model. |
|
@sdodson @smarterclayton, |
| content: | | ||
| openshift_group_type: {{ openshift_aws_node_group_type }} | ||
| {% if openshift_aws_node_group_type != 'master' %} | ||
| - path: /etc/origin/node/csr_kubeconfig |
There was a problem hiding this comment.
I'd prefer to call this bootstrap.kubeconfig to be consistent with its use and other kubeconfig files. Can be a followup.
|
/test logging |
|
|
||
| openshift_master_client_binary: "{{ openshift.common.client_binary if openshift is defined else 'oc' }}" | ||
|
|
||
| openshift_master_config_imageconfig_format: "{{ oreg_url if oreg_url != '' else 'registry.access.redhat.com/openshift3/ose-${component}:${version}' }}" |
There was a problem hiding this comment.
Don't we already have this in another form?
There was a problem hiding this comment.
I think the one that is used is oreg_url so I stayed with it. I'm open to change here.
|
@kwoodson: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
michaelgugino
left a comment
There was a problem hiding this comment.
I would like to see a note in the documentation or in the plays themselves that indicates the provisioning parts are still under active development.
I agree, I think we'd forego docs.openshift.com documentation for now but we should make it clear in playbooks/aws/README.md that these are alpha quality. |
|
We definitely need to split openshift-cluster/config.yml into three equal playbooks that can be called independently - master, node, and hosted/post-install. Bootstrapping needs master up to get the bootstrap.kubeconfig, and ideally as kenny notes we want to:
Is that slated yet? |
|
I opened up this PR this morning on something I had been testing. #5846. I'd like to continue this discussion in that PR. |
These are provisioning updates and features that allow node bootstrapping.
List of updates:
openshift_node_bootstrapin ami creation.Instead of using a template for the node-config.yaml, we call
oc adm create-node-config. We have a list of edits that occur to clean up the generation before it is specialized for each node group. Once each node group has specialized their own copy they are placed in the kube-system namespace with the name node-config- configmap.This is going to require code changes from @smarterclayton to take the configmap and lay it down as the node-config.yaml.