* Move operator API to separate dir
* Update linter settings
* Add make gen files
* Add values field to gateways
* Make gen
* Add enablement for gateways
* Remove CoreDNS from core components list
* istio-api: add consecutive_5xx_errors for outlier detection
This CL adds consecutive_5xx_errors field in OutlierDetection.
This field describes the number of 5xx errors before a host is
ejected from the connection pool.
I made changes to destination_rule.proto, the other files are auto-generated.
Change-Id: Ib5097b3c6bf3ea2b8b2f857491537acb674ae1ff
Reviewed-on: https://gerrit.musta.ch/c/public/istio-api/+/195
Reviewed-by: Brian Wolfe <brian.wolfe@airbnb.com>
Reviewed-by: Jungho Ahn <jungho.ahn@airbnb.com>
Reviewed-by: Weibo He <weibo.he@airbnb.com>
* Revert "istio-api: add consecutive_5xx_errors for outlier detection"
This reverts commit 064b737396200a84ed5fd6303ae6b68b48c569b3.
Reason for revert: decided to deprecate consecutive_errors
Change-Id: I95e3191db30711b1ce7abdebe7639de4899f2ab1
Reviewed-on: https://gerrit.musta.ch/c/public/istio-api/+/163
Reviewed-by: Jungho Ahn <jungho.ahn@airbnb.com>
* istio-api: deprecate consecutive_errors and add gateway & 5xx errors
With the original consecutive_errors design, there is no way to turn
off consecutive gateway errors. This CL deprecate the field and add two
new fields: consecutive_gateway_errors and consecutive_5xx_errors.
See discussions here: https://github.com/istio/api/issues/909
Change-Id: I0e98990d194216cef842fb792a76a5f59b6e674e
Reviewed-on: https://gerrit.musta.ch/c/public/istio-api/+/199
Reviewed-by: Jungho Ahn <jungho.ahn@airbnb.com>
Reviewed-by: Weibo He <weibo.he@airbnb.com>
* istio-api: consecutive 5xx defaults to 5, gateway defaults to 0
This CL changes the description of consecutive_5xx_errors and
consecutive_gateway errors. 5xx defaults to 5 and gateway defaults to 0.
Change-Id: I6c3b29cf92df1c972a7850a726eb159b5e23bf90
Reviewed-on: https://gerrit.musta.ch/c/public/istio-api/+/211
Reviewed-by: Jungho Ahn <jungho.ahn@airbnb.com>
* istio-api: reword consecutive 5xx & gateway descriptions
This CL rewords the descriptions of consecutive 5xx & gateway as
suggected in https://github.com/istio/api/pull/1189/files.
Change-Id: Ia95c03da78a2c9f12c8762b9d8fb95e7add08516
Reviewed-on: https://gerrit.musta.ch/c/public/istio-api/+/214
Reviewed-by: Jungho Ahn <jungho.ahn@airbnb.com>
* Add forward spec to JWTRule
* Drop forward_original
* Rename forward-xxx to output-
* Update proto.lock due to Jwt -> JwtRule rename
* Add back the option to keep the original token
* Update comment for less google specific
* Rename retain_ to forward_
* Fix rebase proto.lock
To support mirroring less than 1% of traffic to a destination, the
mirror_percent field should provide specification of percentages less
than 1. Envoy permits mirroring fractions as small as 1 in 1,000,000.
The Delay and Abort messages already encountered this issue and
solved it by using a Percent (== double) field called percentage instead
of an integer field called percent.
Here, we support small fractions in mirroring using the same pattern,
using mirror_percentage in place of mirror_percent and deprecating the
mirror_percent field.
When reading mirror_percentage, we will need to handle rounding
of numbers near 1.0e-6 carefully because the floating point
representation will not be exact.
* Add RequestAuthetication API
* Address comments
* Make JWTHeader type to define header with prefix
* Revert go.sum
* Address more comments
* Add blank line to end of file
* Update JwtHeader field
* Rename JwtHeader to JWTHeader for consistency
* Update security/v1beta1/jwt.proto
Co-Authored-By: Sven Mawson <sven@google.com>
* Update make gen
* Regenerate file after rebase
* Update comment
* Rebase
* Move locality load balancer settings to destination rule and use it in config.
* Add proto generated files with protolock
* Update based on proto run.
* Fix conventions
* Additional changes after generation
* Update the protolock status files.
* Add locality load balancer settings under port traffic policy
* Moved locality load balancer settings under load balancer settings.
* Remove extra lines added.
* Update after make gen.
* use field_behavior opiton for required fields
* modify makefile to replace import path for field_behavior
* generate after image update
* changes after comments from policy and telemetry team
* regen after changes
* update networking and rebase
This PR establishes a way to disable telemetry reporting via Mixer. This
is part of the transition to the extensibility v2 architecture in which
there will be no Mixer in Istio. We need a mechanism to allow
selectively disabling Mixer for experimentation, development, and
migration.
This option is hidden, as it is meant only for experimental usage.
This new field is needed, as setting `mixer_report_server` to be empty
would break TCP reporting during the transition state. When TCP support
reaches parity, this field can be retired in favor of unsetting
`mixer_report_server`.
Related issue: https://github.com/istio/istio/issues/15935
Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com>
* feat(mixerclient): add field to signal mixerclient to ignore forwarded attributes
Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com>
* add clarification on precedence
Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com>
- Fix some broken dependency tracking.
- Remove a superfluous proto import to get rid of a warning.
- Explicitly select an older build-tools container version, since
the current one has some problems building the protos.
- Make more human-readable
- Properly track all dependencies
- Simplify container usage
- Combine rules to reduce # tool invocations
- Fix missing python binding for rbac protos.
- Include html link checking as part of linting.
- Retire CircleCi job, since that's now taken care of by the above linting change.
As a result of these changes, a full rebuild takes considerably less time
(1/10th maybe)
Jason Wang