Fix issues identified during API review#254
Fix issues identified during API review#254istio-testing merged 3 commits intoistio-ecosystem:mainfrom
Conversation
nrfox
left a comment
There was a problem hiding this comment.
LGTM all issues I found are fixed
|
/retest |
dgn
left a comment
There was a problem hiding this comment.
lgtm except for one question. Adding hold in case you want to make further changes, feel free to remove
/hold
| enabled: | ||
| description: Controls whether ambient redirection is enabled | ||
| type: boolean | ||
| ipv6: |
There was a problem hiding this comment.
hmm. as we don't support ambient yet, maybe we want to remove this for now?
|
just noticed that this still contains the sail-operator/api/v1alpha1/values_types.gen.go Lines 410 to 412 in ac99ae0 I can submit a patch to remove it upstream and then update the commit we use in a separate PR |
Go ahead and remove it from upstream. But you don't need to update the commit, because I'm working on making the API transformer use the commits in go.mod, so your changes will automatically be pulled in when istio is updated. |
Signed-off-by: Marko Lukša <mluksa@redhat.com>
Signed-off-by: Marko Lukša <mluksa@redhat.com>
Signed-off-by: Marko Lukša <mluksa@redhat.com>
|
/hold cancel |
* Fix issues identified during API review Signed-off-by: Marko Lukša <mluksa@redhat.com> * Pull in latest upstream changes Signed-off-by: Marko Lukša <mluksa@redhat.com> * Remove CNIConfig.Ambient Signed-off-by: Marko Lukša <mluksa@redhat.com> --------- Signed-off-by: Marko Lukša <mluksa@redhat.com> Signed-off-by: Daniel Grimm <dgrimm@redhat.com>
* upstream/main: Ensure `make gen-check` works when go mod cache is empty (openshift-service-mesh#270) Introduce RemoteIstio (openshift-service-mesh#202) api_transformer: use `go env` to detect mod cache dir (openshift-service-mesh#269) Add field values.experimental to API (openshift-service-mesh#264) Fix errors in tables for api reference documentation (openshift-service-mesh#263) Generate CNIGlobalConfig from GlobalConfig automatically (openshift-service-mesh#260) Fix errors in api reference doc (openshift-service-mesh#262) Rename `addTags` to `addComments` in API transformer (openshift-service-mesh#259) Add relatedImages to ClusterServiceVersion (openshift-service-mesh#243) Generate API from versions defined in go.mod (openshift-service-mesh#258) Fix issues identified during API review (openshift-service-mesh#254) # Conflicts: # bundle/manifests/sailoperator.clusterserviceversion.yaml
* Fix issues identified during API review Signed-off-by: Marko Lukša <mluksa@redhat.com> * Pull in latest upstream changes Signed-off-by: Marko Lukša <mluksa@redhat.com> * Remove CNIConfig.Ambient Signed-off-by: Marko Lukša <mluksa@redhat.com> --------- Signed-off-by: Marko Lukša <mluksa@redhat.com> Signed-off-by: Daniel Grimm <dgrimm@redhat.com>
* upstream/main: Add `RemoteIstio` to API concepts in docs (openshift-service-mesh#272) Ensure `make gen-check` works when go mod cache is empty (openshift-service-mesh#270) Introduce RemoteIstio (openshift-service-mesh#202) api_transformer: use `go env` to detect mod cache dir (openshift-service-mesh#269) Add field values.experimental to API (openshift-service-mesh#264) Fix errors in tables for api reference documentation (openshift-service-mesh#263) Generate CNIGlobalConfig from GlobalConfig automatically (openshift-service-mesh#260) Fix errors in api reference doc (openshift-service-mesh#262) Rename `addTags` to `addComments` in API transformer (openshift-service-mesh#259) Add relatedImages to ClusterServiceVersion (openshift-service-mesh#243) Generate API from versions defined in go.mod (openshift-service-mesh#258) Fix issues identified during API review (openshift-service-mesh#254) # Conflicts: # bundle/manifests/sailoperator.clusterserviceversion.yaml
) (istio-ecosystem#669) (istio-ecosystem#254) We use `-ldflags` to set the `istioversion.versionsFilename` variable, but this only works when building the binary. It doesn't work when running ginkgo-based e2e tests. When the `versionsFilename` is not set via ldflags, it will now use the environment variable `VERSIONS_YAML_FILE`. If this env var isn't set, we default to `versions.yaml`. (cherry picked from commit 148eb64) Signed-off-by: Marko Lukša <mluksa@redhat.com>
) (istio-ecosystem#669) (istio-ecosystem#254) We use `-ldflags` to set the `istioversion.versionsFilename` variable, but this only works when building the binary. It doesn't work when running ginkgo-based e2e tests. When the `versionsFilename` is not set via ldflags, it will now use the environment variable `VERSIONS_YAML_FILE`. If this env var isn't set, we default to `versions.yaml`. (cherry picked from commit 148eb64) Signed-off-by: Marko Lukša <mluksa@redhat.com>
No description provided.