Prafull Ladha comments

Results 22 comments of


                                            Prafull Ladha

use a NetworkPolicy instead of kube-rbac-proxy

Hi @camilamacedo86 @estroz Network policies are implemented by CNI(container Network Interface) in the cluster. It means the users which are deploying kubebuilder's operator on such cluster where CNI doesn't support...

On hook failure, the cleanup mechanism should also run on all previous hooks

IMHO execHook function can not be properly covered with unit tests. The execHook function creates hooks resources reading from the release and deletes the successful/failed hooks resources based on the...

On hook failure, the cleanup mechanism should also run on all previous hooks

@bacongobbler Can you please have a look at above comment. Thanks :)

[Regression] Decommission is broken

I will take a look

[Regression] Decommission is broken

I have tried this and on the latest version I am not able to reproduce this issue: When you see the UI it shows 3 Live nodes and 1 Decommissioned...

CI Process moving forward

The option to use github container registry gives us advantages of both approach. 1. You can use `pull_request` in the github actions. It give the Read only access to `GITHUB_TOKEN`...

CI Process moving forward

If we go ahead with ghcr.io approach, then we need to create the GITHUB_TOKEN (Personal Access Token of the OWNER) secret added into the repo for the workflows to be...

Operator crashes when creating vcheck pod if an invalid value of topologySpreadConstraints.whenUnsatisfiable is given

@himanshu-cockroach can you please have a look?

Assign existing/custom `schedulerName` to StatefulSet

Right now we don't expose the schedule Name to allow our pods to be scheduled by custom schedular. We have to take it as an enhancement.

Support Rolling Upgrades for the cockroachdb installed through helm chart

@udnay Please share your thoughts on this