-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add asset for DNS config #934
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
Add asset for DNS config #934
Conversation
|
Still testing. /hold |
|
This is largely cargo-culting from #717, so if there's better example to follow, please point me to it. |
|
/hold cancel |
|
Can you squash the fixup commit in? We also prefer having the vendor bump in it's own separate commit, to make it easier to distinguish between human- and machine-generated changes (see #717 for an example of this). But the vendor bump here is small enough that I'm fine leaving that in the same commit as the changes you wrote yourself if you don't want to bother splitting it out. |
Update openshift/api to a level which includes DNS config.
Add a `config.openshift.io/DNS` instance to the cluster to expose DNS configuration. * Update the `openshift/api` package to a version containing the new config type. * Generate the `config.openshift.io/DNS` custom resource definition manifest. * Generate the CRD instance manifest populated with base domain from the install config. This enables consumers of DNS configuration to migrate away from install config.
78ccbef to
dd6d6d5
Compare
|
@wking my team also uses separate commits for dependency updates, so no problem... split dependency bump into a new commit and squashed other changes. PTAL |
|
@abhinavdahiya @wking @crawford PTAL, I have another one coming after this for cloud provider |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
2018/12/18 17:50:29 Copying artifacts from e2e-aws into /logs/artifacts/e2e-aws
2018/12/18 17:50:29 error: unable to signal to artifacts container to terminate in pod e2e-aws, triggering deletion: could not run remote command: unable to upgrade connection: container not found ("artifacts")
2018/12/18 17:50:29 error: unable to retrieve artifacts from pod e2e-aws: could not read gzipped artifacts: unable to upgrade connection: container not found ("artifacts")
E1218 17:50:34.426002 11 event.go:203] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:".15717eae579f5fe6", GenerateName:"", Namespace:"ci-op-q60jbthr", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Initializers:(*v1.Initializers)(nil), Finalizers:[]string(nil), ClusterName:""}, InvolvedObject:v1.ObjectReference{Kind:"", Namespace:"ci-op-q60jbthr", Name:"", UID:"", APIVersion:"", ResourceVersion:"", FieldPath:""}, Reason:"CiJobFailed", Message:"Running job pull-ci-openshift-installer-master-e2e-aws for PR https://github.com/openshift/installer/pull/934 in namespace ci-op-q60jbthr from author ironcladlou", Source:v1.EventSource{Component:"ci-op-q60jbthr", Host:""}, FirstTimestamp:v1.Time{Time:time.Time{wall:0xbefe6aba9949bbe6, ext:11451145957064, loc:(*time.Location)(0x19f83a0)}}, LastTimestamp:v1.Time{Time:time.Time{wall:0xbefe6aba9949bbe6, ext:11451145957064, loc:(*time.Location)(0x19f83a0)}}, Count:1, Type:"Warning", EventTime:v1.MicroTime{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'events ".15717eae579f5fe6" is forbidden: unable to create new content in namespace ci-op-q60jbthr because it is being terminated' (will not retry!)
2018/12/18 17:50:35 Ran for 3h10m52s
error: could not run steps: could not wait for pod to complete: could not wait for pod completion: pod e2e-aws was already deletedHmm 😕 /retest |
|
/retest |
|
/cc @csrwng |
|
the worker node never joined... show that the instance was created. @aveshagarwal also say this happening on his cluster. |
|
Not sure it's relevant, but the operator is getting throttled by AWS when trying to look up the hosted zone, although it succeeds after a few minutes: The above repeats 16 times before reconciliation eventually succeeds: |
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/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. |
Add a
config.openshift.io/DNSinstance to the cluster to expose DNS configuration.openshift/apipackage to a version containing the new config type.config.openshift.io/DNScustom resource definition manifest.This enables consumers of DNS configuration to migrate away from install config.
Related to openshift/api#146.
/cc @openshift/sig-network-edge