Re: registry deletion
Note that any command that can generate objects can be an input to delete: oadm registry -o json | oc delete -f - It won’t delete objects you personally created, but is a good way to rewind. On Nov 28, 2017, at 6:13 PM, Ben Parees wrote: On Tue, Nov 28, 2017 at 6:06 PM, Brian Keyes wrote: > I want to delete this docker registry and start over, this is the command > that I think was run to create it > > oadm registry --config=/etc/origin/master/admin.kubeconfig > --service-account=registry > > > > oadm registry delete or something like that ??? > sorry, there's no command to delete it. You should be able to just delete the deploymentconfig (oc delete dc docker-registry -n default) and then run oadm registry again to recreate it, however. You'll get some errors because of resources that already exist, but it'll get you a new registry pod. But i might also ask why you feel you need to delete the registry to get back to a clean state. > > thanks > -- > Brian Keyes > Systems Engineer, Vizuri > 703-855-9074 <(703)%20855-9074>(Mobile) > 703-464-7030 x8239 <(703)%20464-7030> (Office) > > FOR OFFICIAL USE ONLY: This email and any attachments may contain > information that is privacy and business sensitive. Inappropriate or > unauthorized disclosure of business and privacy sensitive information may > result in civil and/or criminal penalties as detailed in as amended Privacy > Act of 1974 and DoD 5400.11-R. > > > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > -- Ben Parees | OpenShift ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: registry deletion
On Tue, Nov 28, 2017 at 6:06 PM, Brian Keyes wrote: > I want to delete this docker registry and start over, this is the command > that I think was run to create it > > oadm registry --config=/etc/origin/master/admin.kubeconfig > --service-account=registry > > > > oadm registry delete or something like that ??? > sorry, there's no command to delete it. You should be able to just delete the deploymentconfig (oc delete dc docker-registry -n default) and then run oadm registry again to recreate it, however. You'll get some errors because of resources that already exist, but it'll get you a new registry pod. But i might also ask why you feel you need to delete the registry to get back to a clean state. > > thanks > -- > Brian Keyes > Systems Engineer, Vizuri > 703-855-9074 <(703)%20855-9074>(Mobile) > 703-464-7030 x8239 <(703)%20464-7030> (Office) > > FOR OFFICIAL USE ONLY: This email and any attachments may contain > information that is privacy and business sensitive. Inappropriate or > unauthorized disclosure of business and privacy sensitive information may > result in civil and/or criminal penalties as detailed in as amended Privacy > Act of 1974 and DoD 5400.11-R. > > > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > -- Ben Parees | OpenShift ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
registry deletion
I want to delete this docker registry and start over, this is the command that I think was run to create it oadm registry --config=/etc/origin/master/admin.kubeconfig --service-account=registry oadm registry delete or something like that ??? thanks -- Brian Keyes Systems Engineer, Vizuri 703-855-9074(Mobile) 703-464-7030 x8239 (Office) FOR OFFICIAL USE ONLY: This email and any attachments may contain information that is privacy and business sensitive. Inappropriate or unauthorized disclosure of business and privacy sensitive information may result in civil and/or criminal penalties as detailed in as amended Privacy Act of 1974 and DoD 5400.11-R. ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
openshift/api and openshift/client-go are authoritative
As of https://github.com/openshift/origin/pull/17477, h ttps://github.com/openshift/api and https://github.com/openshift/client-go are the authoritative source of the OpenShift API types and the OpenShift external clients. The external types and go client are no longer present in https://github.com/openshift/origin. This makes it possible to interact with an OpenShift cluster without trying to vendor openshift/origin and it changes the way that API changes are merged. To make an API change in 3.8+: 1. open a pull with the external types to openshift/api and get it reviewed, approved, and merged 2. bump the vendored dependencies in openshift/client-go, regenerate (make generate build), and get it merged. 3. bump the vendored dependencies in openshift/origin (hack/update-deps.sh), update your internal types, and start serving your new API. For forks, you will have to merge into the appropriate branches of the various repositories. ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
oc cluster up default subdomain
I'm trying to spin up a development environment where I can run an openshift-ansible playbook against an 'oc cluster up' cluster. It's working except for the default subdomain does not match, causing TLS cert error: oauthproxy.go:582: error redeeming code (client:172.17.0.1:52368): Post https://127.0.0.1.nip.io:8443/oauth/token: x509: certificate is valid for prometheus.openshift-metrics.svc, prometheus.openshift-metrics.svc.cluster.local, not 127.0.0.1.nip.io I would expect that 'oc cluster up --routing-suffix=127.0.0.1.nip.io' would configure the subdomain. How can I configure this? ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
