[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: okd web console custom SSL certificate


If you can I'd recommend OpenShift 4.x, however, if you want to stay on 3.11, then I'd recommend an ansible based install. It is much more configurable than oc cluster up.  

There is an "all-in-one" inventory where it's just a single node. https://github.com/openshift/openshift-ansible/blob/release-3.11/inventory/hosts.localhost

That way you can let ansible install the certificates and configure the master-config for you, and it will be a lot more repeatable.



On Tue, 24 Mar 2020 at 02:33, mcom <mcom mcompany pl> wrote:

Maybe you can give me some hint as I've just stucked with okd web
console custom SSL certificate.I have all in one openshift cluster
(ubuntu 18, downloaded
and started by oc cluster up --public-hostname="myip" ); I was trying to
by making changes (in my case) in
openshift.local.clusterup/kube-apiserver/master-config.yaml but so for
with no luck (despite that it's not logical if I change certificate for
API then it load my certificate but whole cluster cannot start which is
logical as certificate doesn't include; when I change
certificate for web console (which should be correct) nothing happen -
cluster starts but with it's own self-generated certificate instead of
my own); I don't have inventory file so I could run ansible playbooks
but as far I'm concern working directly on master-config should be also
possible (or maybe I'm wrong) - could you give me some hint (my OS is
ubuntu - not centos so many documentation cannot be directly applied
along with ansible playbooks as even paths are not the same)

MCOM Wojciech Matys
Doradztwo IT & Rozwiazania Sieciowe
tel. +48 604915987
e-mail: mcom mcompany pl

users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]