Skip to content

Add a gw/vs for kiali#8971

Merged
istio-testing merged 3 commits intoistio:masterfrom
sdake:kiali_gateway
Sep 29, 2018
Merged

Add a gw/vs for kiali#8971
istio-testing merged 3 commits intoistio:masterfrom
sdake:kiali_gateway

Conversation

@sdake
Copy link
Copy Markdown
Member

@sdake sdake commented Sep 26, 2018

Previously ingress was required to use Kiali. With this change
it is possible to use kiali using ingressgateway as per other
telemetry-gateway behavior.

I recognize this isn't the perfect organization - will get there
over time with multiple PRs.

Previously ingress was required to use Kiali.  With this change
it is possible to use kiali using ingressgateway as per other
telemetry-gateway behavior.

I recognize this isn't the perfect organization - will get there
over time with multiple PRs.
@sdake
Copy link
Copy Markdown
Member Author

sdake commented Sep 26, 2018

/assign @gyliu513

@sdake
Copy link
Copy Markdown
Member Author

sdake commented Sep 26, 2018

/assign @GregHanson

targetPort: 8060
name: tcp-citadel-grpc-tls
# Addon ports for kiali are enabled in gateway - but will only redirect if
# the gateway focnfiguration for the various components are enabled.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

s/focnfiguration/configuration

namespace: {{ .Release.Namespace }}
spec:
selector:
istio: {{ .Values.gatewayName }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It's not required that the selector be istio: <name>, it could be arbitrary labels. We should change values.yaml to take selector, and provide default value istio: ingressgateway.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I prefer that we hardcode the selector here as istio: ingressgateway. As we can see the default ingress gateway in istio only has two labels as below:

  labels:
      app: istio-ingressgateway
      istio: ingressgateway

If we allow end user to set arbitrary labels in values.yaml, the Gateway may not work if it cannot select an ingress gateway via the selector.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@gyliu513 sure I can hardcode the selector and agree it would be better to do so. Less chance for an operator to crater their install. I'm not sure why @douglas-reid chose to make this configurable. Will remove that configurability across the install codebase in a followup PR.

Copy link
Copy Markdown
Member Author

@sdake sdake Sep 27, 2018

Choose a reason for hiding this comment

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

@ZackButcher sure - makes sense. I do agree with @gyliu513 's position that we should simplify this part by hardcoding. I don't see any good reason to make the selector here configurable given the nature of exposing services via ingressgateway. This saves on the expense of introducing another LoadBalancer service type, and the logistics of managing that IP.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@sdake @ZackButcher It is configurable because that was what was asked for. At the time of the PR, the feeling was that while some deployments would want to expose it via "ingressgateway" others may only have wanted to make it exposed via "ilbgateway" or whatever. This was an explicit part of the negotiations around the telemetry-gateway PR. I don't think we should hard-code it. I'm fine with having the selector itself be part of the configuration, however.

@codecov
Copy link
Copy Markdown

codecov bot commented Sep 27, 2018

Codecov Report

Merging #8971 into master will increase coverage by 1%.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #8971    +/-   ##
=======================================
+ Coverage      69%     70%    +1%     
=======================================
  Files         418     418            
  Lines       38551   38149   -402     
=======================================
- Hits        26587   26448   -139     
+ Misses      10715   10475   -240     
+ Partials     1249    1226    -23
Impacted Files Coverage Δ
pilot/pkg/config/kube/ingress/status.go 22% <0%> (-25%) ⬇️
pilot/pkg/model/authorization.go 72% <0%> (-8%) ⬇️
pkg/mcp/creds/watcher.go 84% <0%> (-5%) ⬇️
pilot/pkg/proxy/envoy/v2/discovery.go 61% <0%> (-5%) ⬇️
galley/pkg/kube/source/listener.go 94% <0%> (-2%) ⬇️
mixer/adapter/servicecontrol/quotaprocessor.go 80% <0%> (-2%) ⬇️
pilot/pkg/model/conversion.go 90% <0%> (-1%) ⬇️
pilot/pkg/model/validation.go 83% <0%> (ø) ⬇️
mixer/adapter/kubernetesenv/cache.go 86% <0%> (ø) ⬇️
mixer/adapter/servicecontrol/reportbuilder.go 89% <0%> (ø) ⬇️
... and 20 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c5eae3...33438a3. Read the comment docs.

replicaCount: 1
hub: docker.io/kiali
tag: v0.6
gatewayName: ingressgateway
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we still need this variable in values.yaml?

host: kiali.{{ .Release.Namespace }}.svc.cluster.local
port:
number: 20001
---
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

we need --- in the end of file?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

it has no impact but would be good to delete @sdake

Copy link
Copy Markdown
Member

@gyliu513 gyliu513 left a comment

Choose a reason for hiding this comment

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

/lgtm

@istio-testing
Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gyliu513

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing istio-testing merged commit 588dadb into istio:master Sep 29, 2018
@jmazzitelli jmazzitelli mentioned this pull request Oct 1, 2018
7 tasks
brian-avery pushed a commit to brian-avery/istio that referenced this pull request Apr 15, 2021
…8971)

* Make trace pod annotation warning more visible.

* Update content/en/docs/tasks/observability/distributed-tracing/configurability/index.md

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

Co-authored-by: Pengyuan Bian <bianpengyuan@google.com>
Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
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.

8 participants