checkpointsw / infinity-next Goto Github PK

Hello, team.

During helm install we see deprecated API calls:

W0531 10:51:23.389750    3808 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0531 10:51:33.477507    3808 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0531 10:51:33.489507    3808 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0531 10:51:33.508508    3808 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0531 10:51:33.508508    3808 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Please update yamls.

Currently the chart cannot be consumed as this repository is not a valid helm repository.
Helm error.
looks like "https://github.com/CheckPointSW/Infinity-Next/tree/main/deployments" is not a valid chart repository or cannot be reached: failed to fetch https://github.com/CheckPointSW/Infinity-Next/tree/main/deployments/index.yaml : 404 Not Found

We are not interested to maintain your helm package in our repositories and would prefer to integrate to a valid chart repository.

Br,
Petteri

Hello, team.

According to this repo - https://github.com/CheckPointSW/Infinity-Next/tree/main/contrib/helmIngressController
To install AppSec into k8s cluster we need to use checkpoint repo from:
helm repo add checkpoint https://raw.githubusercontent.com/CheckPointSW/charts/master/repository/

But this repo contains only cp-resource manager:
helm search repo checkpoint
NAME CHART VERSION APP VERSION DESCRIPTION
checkpoint/cp-resource-management 1.09.3 v1.1.0 A Helm chart for CloudGuard Workload Security

How to fix this issue?

When attempting to deploy the helm chart in eks, nginx will not properly pass traffic because
proxy-protocol in the configmap is commented out.

A separate helm chart will be created for eks in a future commit. In the meantime, you can edit the configmap.yaml, uncomment the proxy-protocol statement, repackage the helm chart and it will work.