Skip to content

Seeing continous provider and gateway-api logs in stdout #1715

@arkodg

Description

@arkodg

Description:

Even when no new resources are applied, seeing the provider continuously reconciling and publishing resources to the gateway-api layer which is recomputing the IRs

023-07-26T21:58:47.477Z	INFO	provider	status/status.go:122	received a status update	{"runner": "provider", "namespace": "", "name": "eg"}
2023-07-26T21:58:47.477Z	INFO	provider.eg	status/status.go:92	status unchanged, bypassing update	{"runner": "provider"}
2023-07-26T21:58:47.477Z	INFO	provider	status/status.go:122	received a status update	{"runner": "provider", "namespace": "default", "name": "backend"}
2023-07-26T21:58:47.477Z	INFO	provider.backend.default	status/status.go:92	status unchanged, bypassing update	{"runner": "provider"}
2023-07-26T21:58:47.477Z	INFO	provider	status/status.go:122	received a status update	{"runner": "provider", "namespace": "default", "name": "eg"}
2023-07-26T21:58:47.477Z	INFO	provider.eg.default	status/status.go:92	status unchanged, bypassing update	{"runner": "provider"}
2023-07-26T21:58:47.491Z	INFO	provider	status/status.go:122	received a status update	{"runner": "provider", "namespace": "default", "name": "eg"}
2023-07-26T21:58:47.492Z	INFO	provider.eg.default	status/status.go:92	status unchanged, bypassing update	{"runner": "provider"}
2023-07-26T21:58:47.500Z	INFO	provider	status/status.go:122	received a status update	{"runner": "provider", "namespace": "default", "name": "eg"}
2023-07-26T21:58:47.500Z	INFO	provider.eg.default	status/status.go:92	status unchanged, bypassing update	{"runner": "provider"}
2023-07-26T21:58:47.511Z	INFO	provider	status/status.go:122	received a status update	{"runner": "provider", "namespace": "default", "name": "eg"}
2023-07-26T21:58:47.511Z	INFO	provider.eg.default	status/status.go:92	status unchanged, bypassing update	{"runner": "provider"}
2023-07-26T21:59:18.416Z	INFO	docker-desktop	kubernetes/controller.go:148	reconciling object	{"namespace": "", "name": "docker-desktop"}
2023-07-26T21:59:18.416Z	INFO	provider	kubernetes/controller.go:437	processing Gateway	{"runner": "provider", "namespace": "default", "name": "eg"}
2023-07-26T21:59:18.416Z	INFO	provider	kubernetes/routes.go:205	processing HTTPRoute	{"runner": "provider", "namespace": "default", "name": "backend"}
2023-07-26T21:59:18.416Z	INFO	provider	kubernetes/controller.go:201	processing Service	{"runner": "provider", "namespace": "default", "name": "backend"}
2023-07-26T21:59:18.416Z	INFO	provider	kubernetes/controller.go:212	added Service to resource tree	{"runner": "provider", "namespace": "default", "name": "backend"}
2023-07-26T21:59:18.416Z	INFO	provider	kubernetes/controller.go:229	added EndpointSlice to resource tree	{"runner": "provider", "namespace": "default", "name": "backend-g5l8q"}
2023-07-26T21:59:18.416Z	INFO	docker-desktop	kubernetes/controller.go:311	reconciled gatewayAPI object successfully	{"namespace": "", "name": "docker-desktop"}
2023-07-26T21:59:18.416Z	INFO	provider	status/status.go:122	received a status update	{"runner": "provider", "namespace": "", "name": "eg"}
2023-07-26T21:59:18.416Z	INFO	provider.eg	status/status.go:92	status unchanged, bypassing update	{"runner": "provider"}
2023-07-26T21:59:18.417Z	INFO	gateway-api	runner/runner.go:79	default/eg:
  accessLog:
    text:
    - path: /dev/stdout
  http:
  - address: 0.0.0.0
    hostnames:
    - '*'
    isHTTP2: false
    name: default/eg/http
    port: 10080
    routes:
    - backendWeights:
        invalid: 0
        valid: 0
      destinations:
      - host: 10.111.56.86
        port: 3000
        weight: 1
      headerMatches:
      - distinct: false
        exact: www.example.com
        name: :authority
      name: default/backend/rule/0/match/0-www.example.com
      pathMatch:
        distinct: false
        name: ""
        prefix: /
	{"runner": "gateway-api", "output": "xds-ir"}
2023-07-26T21:59:18.417Z	INFO	gateway-api	runner/runner.go:81	default/eg:
  proxy:
    listeners:
    - address: ""
      ports:
      - containerPort: 10080
        name: http
        protocol: HTTP
        servicePort: 80
    metadata:
      labels:
        gateway.envoyproxy.io/owning-gateway-name: eg
        gateway.envoyproxy.io/owning-gateway-namespace: default
    name: default/eg
	{"runner": "gateway-api", "output": "infra-ir"}

Repro steps:
Quickstart

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Environment:

Include the environment like gateway version, envoy version and so on.

Logs:

Include the access logs and the Envoy logs.

Metadata

Metadata

Assignees

Labels

kind/bugSomething isn't working

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions