Workflow Fixes - Move secrets to GitHub secrets panel

[ggurjar333]

Problem Statement: https://github.com/LoveofSportsLLC/NFL/actions/workflows/be.yaml?query=is%3Afailure https://github.com/LoveofSportsLLC/NFL/actions/workflows/fe.yaml?query=is%3Afailure

The git action is failing when I commit anything to the github, which stops the website from updating in kubernetes. https://learn.microsoft.com/en-us/azure/developer/github/connect-from-azure?wt.mc_id=searchAPI_azureportal_inproduct_rmskilling&sessionId=3e0369dd88ee4c79a2463d0576fe1d65&tabs=azure-portal%2Cwindows

Drill down the secrets: Accessing Secrets in Kubernetes for GitHub Transfer:

• Use kubectl to access your Kubernetes cluster and retrieve the secrets.
• Secrets are stored in base64 encoding, so decode them to get the actual values.
• For security, avoid hardcoding secrets in your GitHub repository. Instead, use GitHub Secrets or encrypted environment variables.
• Use GitHub Actions or a similar CI/CD pipeline to inject these secrets into your deployment process when needed.

To view Kubernetes cluster secrets in Azure Portal, follow these steps:

• Log in to Azure Portal: Open your web browser and go to the Azure Portal (portal.azure.com). Log in with your credentials.
• Navigate to Kubernetes Services: On the Azure Portal home page, search for "Kubernetes services" in the search bar and select it from the search results.
• Select Your Cluster: In the Kubernetes services section, you'll see a list of your Kubernetes clusters. Select the cluster where your secrets are stored.
• Access Kubernetes Dashboard: Within the selected Kubernetes cluster, find and click on the "Kubernetes dashboard" option. This action opens the Kubernetes web user interface.
• Navigate to Secrets: In the Kubernetes dashboard, navigate to the “Secrets” section. This is typically found under the "Configuration" category in the dashboard's sidebar menu.
• View Secrets: Once in the Secrets section, you will see a list of all the secrets stored in your Kubernetes cluster. You can click on a specific secret to view its details.

Solution:

• Move the secrets from Kubernetes cluster to Github secrets panel.

[codeautopilot[bot]]

Your organization has reached the subscribed usage limit. You can upgrade your account by purchasing a subscription at Stripe payment link

_Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect._ Current plan usage: 100.41% **Have feedback or need help?** [Discord](https://discord.gg/r72ykfvyx7) [Documentation](https://docs.codeautopilot.com/) [support@codeautopilot.com](mailto:support@codeautopilot.com)

[zepor]

are there still particular secrets you have issues with? if yea i can get them added, otherwise we can probably close this one