Skip to content

[VC-35373] Add missing VenafiConnection templates and values to the Helm chart #557

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.

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

Closed

Conversation

wallrj
Copy link
Member

@wallrj wallrj commented Aug 16, 2024

Stacked on #552

Ref: VC-35373

@wallrj wallrj force-pushed the VC-35373-venafi-connection-helm-chart branch from 36cce94 to 396bdd6 Compare August 16, 2024 17:02
@maelvls maelvls force-pushed the venconn branch 2 times, most recently from 3833300 to aadc8b2 Compare August 19, 2024 19:26
@wallrj wallrj force-pushed the VC-35373-venafi-connection-helm-chart branch from 396bdd6 to 36f97a0 Compare August 20, 2024 08:13
…on-lib

The venafi-connection-lib library uses more recent versions of the
dependencies in the Venafi Kubernetes Agent. When I ran

  export GOPRIVATE=github.com/jetstack
  go get github.com/jetstack/venafi-connection-lib@latest

most of the dependencies in this project got updated. This commit
captures these changes.
…n=name

I've also added the flag --venafi-connection-namespace as well as the
flag --install-namespace that is only needed when running the agent
out-of-cluster (this is only useful for testing purposes).
Let's pin venafi-connection-lib to the latest commit on main until we
decide to release a new version of venafi-connection-lib (if we actually
do).
@wallrj wallrj force-pushed the VC-35373-venafi-connection-helm-chart branch from 5fca3a3 to b3e1b53 Compare August 20, 2024 11:03
@maelvls maelvls force-pushed the venconn branch 2 times, most recently from f162ad7 to 4f368fa Compare August 20, 2024 11:51
@wallrj wallrj force-pushed the VC-35373-venafi-connection-helm-chart branch from b3e1b53 to 87817e2 Compare August 20, 2024 11:53
@maelvls maelvls force-pushed the venconn branch 12 times, most recently from 83a2190 to 4ec8495 Compare August 20, 2024 14:42
@maelvls maelvls force-pushed the venconn branch 4 times, most recently from 998019a to 388949e Compare August 20, 2024 14:50
@wallrj wallrj force-pushed the VC-35373-venafi-connection-helm-chart branch 2 times, most recently from 86c9b2f to c9f05bb Compare August 20, 2024 16:00
Note that I should probably have gone with a fake of the
ConnectionHandler instead of an envtest. We will move to the fake later
on.

I added the venaficonnection CRDs manually for now. I have a PR to
automate pulling these CRDs from the venafi-connection-lib project:
jetstack#556

For now, I added these manifests manually with the following commands:

  gh pr checkout 556
  git checkout -
  git checkout step1-makefile-modules -- deploy/charts/venafi-kubernetes-agent/templates/venafi-connection-crd{,.without-validations}.yaml
Not sure why or who is adding this line, probably "go work init". I
don't know whether it would be useful, either.

Also, the version "go 1.22.0" was causing errors in CI [1]:

```
go: errors parsing go.mod:
/__w/jetstack-secure/jetstack-secure/go.mod:3: invalid go version '1.22.0': must match format 1.23
/__w/jetstack-secure/jetstack-secure/go.mod:5: unknown directive: toolchain
```

[1]: https://github.com/jetstack/jetstack-secure/actions/runs/10375056958/job/28723891036?pr=552
@wallrj wallrj force-pushed the VC-35373-venafi-connection-helm-chart branch from c9f05bb to 59901a7 Compare August 20, 2024 16:02
@wallrj wallrj changed the title WIP: [VC-35373] Add missing VenafiConnection templates and values to the Helm chart [VC-35373] Add missing VenafiConnection templates and values to the Helm chart Aug 20, 2024
@maelvls maelvls force-pushed the venconn branch 3 times, most recently from e2545c6 to f1f175c Compare August 20, 2024 16:21
@wallrj
Copy link
Member Author

wallrj commented Aug 20, 2024

Supplanted by #559

@wallrj wallrj closed this Aug 20, 2024
@wallrj wallrj deleted the VC-35373-venafi-connection-helm-chart branch August 20, 2024 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants