![]() You can use this window after the application has been installed to perform any changes you may wish to be captured, such as setting a few default options within the application. Next we will be shown the Prepare Computer screen. If desired you can turn off Windows Search from this page, I'd recommend doing this as it'll result in a cleaner package. The tool will automatically install the packaging driver if it's not already installed, and will disable Windows Update for the duration of the packaging process. #INSTALL XML NOTEPAD WHEN LOGGED IN GPO UPDATE# Wait for the preparations to complete, then disable Windows Search if desired. Next you will need to select the installer file, and pass any parameters (e.g. This installer does not need to reside on the virtual machine - the packaging tool will copy it across and execute it for you. For this example I have been original and imaginative and used Notepad++. Select to sign with a certificate, find your PFX file and enter the password used when the PFX was created. #INSTALL XML NOTEPAD WHEN LOGGED IN GPO PASSWORD# sha256/timestamp Finally you will need to enter a timestamp server URL. The only one I could find from a quick google that worked at time of writing was the Symantec one. Providing the time stamp URL is highly recommended - if the package is signed without timestamping, it will no longer install once the certificate has expired. #INSTALL XML NOTEPAD WHEN LOGGED IN GPO INSTALL# #INSTALL XML NOTEPAD WHEN LOGGED IN GPO FREE#.#INSTALL XML NOTEPAD WHEN LOGGED IN GPO PASSWORD#.#INSTALL XML NOTEPAD WHEN LOGGED IN GPO CODE#.#INSTALL XML NOTEPAD WHEN LOGGED IN GPO UPDATE#.#INSTALL XML NOTEPAD WHEN LOGGED IN GPO INSTALL#.It seems in v5 this secret is called ".cluster-cert": I manually extracted the client.crt and client.key files from this.Īfter fixing the above, the pgo client still can't connect via the api-server, because the postgres-operator installation (helm release) did not install svc/postgres-operator, so the port-forward via the api-server does not work. pgo client also can't find the next secret: pgo.tls.I manually created such a secret, providing "username" and "password" data, which worked. I used the helm installation for v5: no such secret. This is because the postgres operator installation did not create that secret. Please ensure that the PostgreSQL Operator has been installed. ![]() pgo client complains: pgouser-admin Secret not found in namespace: postgres-operator.I had to work around some inconsistencies between 4.7.3 and 5.0.4 installation documentation.No documentation for client in latest I have now installed the 4.7.3 client as per your link.Not sure yet if client certs work, since I can't connect to the api-server URL.Don't know what username:password should be in pgouser file.No svc/postgres-operator, so I can't set up a port-forward to the pgo api-server.Now pgo still complains that it can't connect to the api-server, because I likely don't have the correct URL. I decoded these into the client cert files and set the env variables. I found one called "xxx- cluster-cert" (where "xxx" is my helm release name), which contained entries for "ca.crt", "tls.crt" and tls.key". I still don't know where to find the username:password.įor the client certificate files, I tried approach, but there is no secret named "pgo.tls". Some other older docs I found refers to a file conf/postgresql-operator/pgouser that is referenced during the cluster installation, but I can see no such file in the example repo that I forked (which is the latest documented way of starting a cluster). I found instructions in the old docs, and created a ~/.pgo/pgouser file, but I didn't know what to use for username:password. Pgo version now complains: "could not find pgouser file". I created a port-forward on 8443 to the only control-plane pod that I could see, and then set PGO_APISERVER_URL to. The older docs that I found said to port-forward to svc/postgres-operator, but there is no such service deployed. Then I tried pgo version, but got a succession of startup errors.įirst, I had to set PGO_APISERVER_URL. It seems this is the latest client file, there is no v5 pgo client? I tried the 4.0.1 installation procedure at and downloaded the 4.7.3 pgo file for Linux. I could get the cluster going, but there's no v5 documentation for the pgo client.
0 Comments
Leave a Reply. |