Philip Sanetra

Results 25 issues of Philip Sanetra

Adds https://github.com/PSanetra/git-semver to about page.

This PR adds support for context-aware ActivationStrategies with custom strategy-dependent contexts. It contains the following changes: * New interface `ContextAwareActivationStrategy` extends the `ActivationStrategy` interface, deprecates the `isActive(FeatureState, FeatureUser)` method and...

It would be nice to extend the default execution parameters config with a `ReadOnlyFs` field. Currently it is only possible to declare that option explicitly on container start (e.g. with...

It would be nice to have a `ClusterCheck` CRD, which could be deployed independently from the Cluster Agent deployment. Currently it is only possible to configure such a check via...

enhancement

The latest changes in the master are not yet available via the Helm chart repository. It would be nice to have a new release with the latest changes.

We are running VerneMQ in a 2-node cluster in Kubernetes. On a restart of a VerneMQ instance we are purging the state of that node, because it is also leaving...

help wanted
Kubernetes

It would be nice to be able to decode parquet files to a human-readable format. Output format could be json, like the visual studio parquet viewer. See https://marketplace.visualstudio.com/items?itemName=dvirtz.parquet-viewer as reference

feature

As far as I can see the ingess controller currently just supports the "non-standard" `X-Forwarded-*` headers. It would be nice to support also the standard [`Forwarded` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded). #### Use case...

help wanted
kind/feature
priority/backlog
good first issue
triage/accepted

As far as I can see the ingess controller currently just supports the "non-standard" X-Forwarded-* headers. It would be nice to support also the standard [Forwarded header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded). Use case Keycloak...

kind/feature
lifecycle/stale
lifecycle/needs-triage

I tried to overwrite the `X-Forwarded-Port` header in a policy, but it seems like envoy ignores this policy. Therefore it would be nice to allow enabling the envoy `append_x_forwarded_port` option...

kind/bug
lifecycle/stale
lifecycle/needs-triage