You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: charts/core/README.md
+25-2Lines changed: 25 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ This chart supports integration with External Secrets Operator for syncing secre
7
7
### Prerequisites
8
8
9
9
ESO requires the following secrets to be defined in `secEnvVars`:
10
+
10
11
-`AZURE_CLIENT_ID` - Azure Service Principal Client ID
11
12
-`AZURE_CLIENT_SECRET` - Azure Service Principal Client Secret
12
13
-`AZURE_TENANT_ID` - Azure Tenant ID
@@ -34,17 +35,39 @@ global:
34
35
### Generated Resources
35
36
36
37
When ESO is enabled, the chart creates:
38
+
37
39
- **ClusterSecretStore**: `<release-name>-cluster-secret-store` - connects to Azure Key Vault
38
40
- **ExternalSecret**: `<release-name>-external-secret` - syncs secrets to `<release-name>-secure-kv`
39
41
40
42
The ESO will use the existing `<release-name>-secure` secret (created from `secEnvVars`) for authentication to Azure Key Vault.
41
43
42
-
# How to test locally
44
+
## Sticky Sessions
45
+
46
+
Enables cookie-based session affinity for Traefik IngressRoutes. **Mutually exclusive with canary deployments** — when `global.canary.enabled` is `true`, sticky config is ignored. Flagger officially doesn't support sticky sessions, as well as it breaks user weighted routing when rollout is happening.
47
+
48
+
### Configuration
49
+
50
+
```yaml
51
+
global:
52
+
ingressRoutes:
53
+
routes:
54
+
- ruleName: private
55
+
sticky:
56
+
enabled: true
57
+
name: my-cookie # default: <release-name>-sticky
58
+
secure: false # default: true
59
+
httpOnly: true # default: true
60
+
sameSite: strict # default: strict
61
+
```
62
+
63
+
## How to test locally
64
+
43
65
1. Install prerequisites as specified in tests requirements.txt
44
66
2. in charts\charts\core type "helm template ." make sure the template renders correctly
45
67
3. in charts\charts\core type "pytest" all tests should pass
46
68
47
-
# How to debug in VS code
69
+
## How to debug in VS code
70
+
48
71
https://code.visualstudio.com/docs/python/testing
49
72
test discovery in subfolders is based on existence of __init__.py file
50
73
to run tests succesfully you need to set test working directory go to File->Preferences->settings, search Tests, select Python and find "Optional working directory for tests." Set it to charts\core
0 commit comments