Infisical Users

set the channel topic: Ask <https://struct.ai|Struct.AI> bot anything. Knowledge Base: <https://questions.infisical.com>

Based on the provided chat documents, there is no explicit mention of Infisical's compatibility with Postgres. Refer to the chat transcripts available for available information on Infisical's features, integrations, and usage.

References:
- <https://questions.infisical.com/kb/t/2Mc2>
- <https://questions.infisical.com/kb/t/2K2ced>
- <https://questions.infisical.com/kb/t/2M3c>
- <https://questions.infisical.com/kb/t/2L8a1>
- <https://questions.infisical.com/kb/t/2Lb77>



Give me a sample config to use Infisical with circle ci

Although none of the referenced documents provide a direct answer to your question, we can gather some information from them regarding the setup of Infisical and its integration with certain services. 

However, a 'Circle CI' specific configuration example is not provided in the given documents. It might be better to consult the official documentation or support forums for Infisical's integration with Circle CI.

References:
- <https://questions.infisical.com/t/2Na>
- <https://questions.infisical.com/t/2Lac1>
- <https://questions.infisical.com/t/2La5e>
- <https://questions.infisical.com/t/2K7181>
- <https://questions.infisical.com/t/2K5a11>



<@U05HGJ8S3GT> how to use token auth with the kubernetes operator?

To use token authentication with the Kubernetes operator, you typically need to create a Kubernetes secret that contains the token. Then, in your Kubernetes operator deployment, you reference this secret to authenticate your requests. 

The process usually involves:

1. **Creating a Service Token:** 
    - Depending on the specific operator and its documentation, you may first need to create a service token within the platform or service that the operator interacts with. This token will be used for authentication.
    
2. **Storing the Token in a Kubernetes Secret:**
    - Use `kubectl` to create a Kubernetes secret that contains the service token. For example:
        ```
        kubectl create secret generic my-operator-secret \
          --from-literal=token=&lt;YOUR_TOKEN&gt; \
          -n &lt;NAMESPACE&gt;
        ```
        Replace `&lt;YOUR_TOKEN&gt;` with your actual service token, and `&lt;NAMESPACE&gt;` with the namespace where your operator will be running.
    
3. **Referencing the Secret in the Operator Deployment:**
    - In the operator's deployment YAML, you need to reference the secret to access the token. This is usually done by setting an environment variable that is populated from the secret. For instance:
    
        ```yaml
        env:
          - name: TOKEN_ENV_VARIABLE_NAME
            valueFrom:
              secretKeyRef:
                name: my-operator-secret
                key: token
        ```
        Replace `TOKEN_ENV_VARIABLE_NAME` with the name of the environment variable that the operator uses to read the token, `my-operator-secret` with the name of your created secret, and `token` with the key under which the token is stored in the Kubernetes secret.
        
4. **Deploy the Operator:**
    - With the secret created and the operator deployment configuration updated, deploy or update your operator in Kubernetes.

It's important to consult the official documentation of the specific Kubernetes operator you are using since the exact variable names, configuration formats, and procedures could vary.

Regarding the transition from service token to client secret as noted in one discussion thread, it seems like replacing the service token with a client secret follows a similar principle. Ensure you update the Kubernetes secret with the new authentication method as per the operator's documentation or release notes for specific instructions.

References:
- <@2K1d87>
- <@2J2bc05>

How can i save a Secret to disk with the infisical-cli like a kubeconfig

Hi Nico! You might wan to ask this in <#C04BSBMQAQ7|> instead :slightly_smiling_face: