Page Comparison

...

1. Rename the obtained metadata (XML) file from the customer to “kfuse.xml” exactly.

OR

1. If the customer provided you with a url to the metadata file, then do a curl on the url and save its output to the “kfuse.xml” file name exactly. Save this directly in the customer’s terminal.

   Code Block
   curl {metadata xml file url} > kfuse.xml

2. In the customer’s cluster and appropriate namespace, run this command

   Code Block
   kubectl create secret generic kfuse-xml --from-file=kfuse.xml

...

B. In the environment values.yaml file -

1. Enable the kfuse-saml flag to true in the “global“ section of the environment file.

2. Set the dnsName tag to the customer’s kloudfuse domain name.

global:
  dnsName: <your kloudfuse domain name>
  kfuse-saml:
    enabled: true

3. Set the flag saml-provider-name to the customer’s SAML provider name in kfuse-auth config.

4. Set the flag existingSecret: "kfuse-auth-saml" in the config section of oauth2-proxy in kfuse-auth section.

5. For example, for Okta as the SAML provider -

kfuse-auth:
  oauth2-proxy:
    config:
      saml-provider-name: "Okta"

Ensure that flag “existingSecret” exists and is non-empty.

...

...

...

existingSecret: "kfuse-auth-saml"

Now, do the general upgrade using the environment’s file.

...

1. Exec into kfuse-configdb shell . using command -

   Code Block
   k exec -it kfuse-configdb-0 -- bash

2. psql into the postgres using command -

   Code Block
   psql -U postgres

3. It will ask for password for postgres. Provide that.

4. Check all tables and if samldb exist database exists using the command-

   Code Block
   \l

5. Delete and create the table samldb

   Code Block
   dropDROP databaseDATABASE samldb; CREATE createdbDATABASE samldb;