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.

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

Fix/fix readme #289

Merged
merged 48 commits into from
Dec 21, 2020
Merged

Fix/fix readme #289

merged 48 commits into from
Dec 21, 2020

Conversation

mariusv
Copy link
Collaborator

@mariusv mariusv commented Nov 13, 2020

fixes #288

icereval and others added 30 commits November 12, 2020 12:21
* kube2iam chart

* set hostNetwork at the spec level

* fixes from code review h/t @mgoodness

* cleanup/style

* linter, host needs to be a dictionary

* move kube2iam to stable
…card support (#387)

* .Values.host.interface shouldn't be quoted

In some network configurations we have to handle traffic to the metadata api
from multiple interfaces - typically the node side of a veth pair, where the
other side lives inside a Pod's network namespace.  We could use the wildcard
functionality in iptables to do this, but setting `host.interface: veth+` in
this chart doesn't work.

This is because the parameter is quoted in the DaemonSet template and kube2iam
ends up sending the parameter it receives on the command-line directly to
`execvp("iptables", ...)`, which means that the parameter stays quoted all the
way into the actual iptables rule. So you end up with a rule that looks like
this:

```shell
iptables -t nat -S PREROUTING | grep 169.254.169.254
-A PREROUTING -d 169.254.169.254/32 -i "veth+" -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.0.0.1:8181
```

this rule only matches an interface named exactly veth+ since the wildcard
character apparently isn't expanded when the interface name is quoted. If we
remove the quoting we can support iptables wildcards and I don't see why it
shouldn't work for exact matching the interface name still.

* Bump version
* Missing chart in helm install statement

Usage: (v2.1.3)
  helm install [CHART] [flags]

* Include chart in install statement
* Fix set flag to use strings as required

* Trim to single line set option

* Managed to stomp the package during rebase

* Consistency of install package
* Added .helmignore
* Updated common labels per proposed best practices
* Split image repository and tag
* Don't quote host interface argument (fix)
* Added verbose option
* Docs
* YAML formatting
* Removed default function in favor of values.yaml
* Pedantic commenting

* No default resources

* Semver-compliant
* [stable/kube2iam] Rolling updates

Also bump to latest image version

* Allow further update strategies
* add rbac support

* solve and edge-case when turning off rbac
Use consistent whitespace in template placeholders
* fix: update default image version to latest

* Bump chart version
* Allow user-managed RBAC

* Add namespaces to ClusterRole
* Set UpdateStrategy using .Capabilities

* Bump chart version
Added a secret resource to allow setting AWS access keys and region
* Add liveness check so kube takes care of kube2iam in the event of any issues

* Configure --app-port to remain consistent with Helm chart value of .host.port

* Bump minor version

* Remove option to disable liveness probe
* patch3

patch3

* patch-2 tables

patch-2 tables
…… (#4535)

* kube2iam update to 0.10.0; fixes 5th generation instance types and cross namespace permissions

* kube2iam adding home to Chart.yaml
* Fix for version comparison from strings to semver

See #3002 for more detail

* Updating maintainers to github ids

* Fixing " error due to wrong " character

* Include pre-releases in the semver ranges

This is important when testing against alpha and beta builds of
Kubernetes along with environments that use pre-releases to denote
things other than pre-releases (e.g., gke denotes the environment
with a pre-releases)
* Update README.md

* Incrementing the chart version
* Support extra container environment variables.

* [stable/kube2iam] Ensure extra container environment variable values are quoted.
* [kube2iam] Add node flag to limit relevant pods

* Update Chart.yaml
* added missing get verb

Signed-off-by: Amir Kibbar <[email protected]>

* bumped version

Signed-off-by: Amir Kibbar <[email protected]>
willfrew and others added 17 commits November 12, 2020 12:21
Changes:
 - Adds ServiceMonitor & Service resources for use with Prometheus Operator.
 - Allows configuring the metrics port option of kube2iam and will
 configure the new named port on the DaemonSet when applicable.
 - Adds docs for all new config params

Bonus:
 - Adds missing docs for `host.port` config param

Signed-off-by: Will Frew <[email protected]>
Signed-off-by: Carlos Panato <[email protected]>
does not change metrics port and requires second custom port

Signed-off-by: George Kaz <[email protected]>
… (#15626)

* Upgrade Kube2iam, Add prometheus service annotations

Signed-off-by: Fabio Todaro <[email protected]>

* Update README

Signed-off-by: Fabio Todaro <[email protected]>
See https://helm.sh/docs/chart_best_practices/#standard-labels

Since the DaemonSet's selector is immutable, this is breaking change and will require a deletion and recreation, hence the major version bump.

Signed-off-by: Peter Rifel <[email protected]>
* [stable/kube2iam] Update version in documentation

Change version from 0.10.4 to 0.10.7

Signed-off-by: Nicolas Vanheuverzwijn <[email protected]>

* Bump chart version from 2.0.0 to 2.0.1

Signed-off-by: Nicolas Vanheuverzwijn <[email protected]>
…bility (#18784)

* [stable/kube2iam] Update the kube2iam apiVersion for k8s 1.16 compatibility

Signed-off-by: Mike Tougeron <[email protected]>

* [stable/kube2iam] fix the selector

Signed-off-by: Mike Tougeron <[email protected]>
…redentials (#21265)

* Allow setting a custom secret name to use for AWS credentials in the event that the secret is populated from outside of helm for security purposes

Signed-off-by: Mike Tougeron <[email protected]>

* [stable/kube2iam] call the variable existingSecret

Signed-off-by: Mike Tougeron <[email protected]>

* Bump minor version for new feature

Signed-off-by: Reinhard Nägele <[email protected]>

Co-authored-by: Reinhard Nägele <[email protected]>
kube2iam v0.10.9 supports 1.17.3 due to client-go version upgrades

Signed-off-by: Marius Voila <[email protected]>
…2717)

* allow to customise livenessProbe parameters

Signed-off-by: Luigi Tagliamonte <[email protected]>

* bump chart version

Signed-off-by: Luigi Tagliamonte <[email protected]>

* document variables in the README

Signed-off-by: Luigi Tagliamonte <[email protected]>
fixes jtblin#288

Signed-off-by: Marius Voila <[email protected]>
@mariusv mariusv mentioned this pull request Nov 13, 2020
@coveralls
Copy link

coveralls commented Nov 13, 2020

Coverage Status

Coverage remained the same at 19.481% when pulling dcc9591 on mariusv:fix/fix-readme into a1b6aa3 on jtblin:master.

@ghost
Copy link

ghost commented Nov 23, 2020

I guess that is not the right url right now:

❯ helm repo add kube2iam https://kube2iam.github.io/charts/
Error: looks like "https://kube2iam.github.io/charts/" is not a valid chart repository or cannot be reached: failed to fetch https://kube2iam.github.io/charts/index.yaml : 404 Not Found

@mariusv
Copy link
Collaborator Author

mariusv commented Nov 23, 2020

@oed-mertenss not until @jtblin creates the Github pages for it

$ helm repo add kube2iam https://buildkite.github.io/charts/
$ helm repo update
$ helm install stable/kube2iam --name my-release
$ helm repo add kube2iam https://kube2iam.github.io/charts/
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably going to be http://jtblin.github.io/kube2iam/. Can someone verify?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested with helm fetch kube2iam --repo http://jtblin.github.io/kube2iam and it seemed to pull the chart down (v2.5.2) just fine.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we please bump the chart version? Since there is a 2.5.3 already on the (now read-only/deprecated) stable repo perhaps 2.5.4 or 2.6.0 is appropriate given the repo move?

@jtblin jtblin merged commit bb97695 into jtblin:master Dec 21, 2020
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.

Fix README for the chart