Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated latest SRS version in README doc to 1.34.2 #842

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+2 −2
Open

Updated latest SRS version in README doc to 1.34.2 #842

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6777bef
Updated latest SRS version in README doc
ravitejamekapega Nov 6, 2024
062d51e
Minor change to fix link to values.yaml file
ravitejamekapega Nov 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/addons/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ When deploying on Azure AKS, you can use an Application Gateway Ingress Controll

After you create the deployment ingress controller, in the Addons Helm chart, disable Traefik (set `traefik.enabled` to `false`), enable AGIC (set `ingress-azure.enabled` to `true`) and add the AGIC gateway configuration details from your AKS deployment.

To authenticate with the AGIC in your AKS cluster, generate a kubernetes secret from an Active Directory Service Principal that is based on your AKS subscription ID. You must encode the Service Principal with base64 and add the result to the `armAuth.secretJSON` field. For details, see the comments in the addons [values.yaml](/values.yaml) or the [AKS runbook](../../docs/Deploying-Pega-on-AKS.md).
To authenticate with the AGIC in your AKS cluster, generate a kubernetes secret from an Active Directory Service Principal that is based on your AKS subscription ID. You must encode the Service Principal with base64 and add the result to the `armAuth.secretJSON` field. For details, see the comments in the addons [values.yaml](./values.yaml) or the [AKS runbook](../../docs/Deploying-Pega-on-AKS.md).

As an authentication alternative, you can configure an AAD Pod Identity to manage authentication access with the AGIC in your cluster via the Azure Resource Manager. For details, see [Set up AAD Pod Identity](https://docs.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-existing#set-up-aad-pod-identity).

Expand Down
2 changes: 1 addition & 1 deletion charts/backingservices/charts/srs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ The service deployment provisions runtime service pods along with a dependency o
</tr>
<tr>
<td rowspan=4> >= 8.6 </td>
<td rowspan=4>1.31.8</td>
<td rowspan=4>1.34.2</td>
<td rowspan=2>< 1.25</td>
<td>Not enabled</td>
<td>7.10.2, 7.16.3 & 7.17.9</td>
Expand Down
Loading