apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:09:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-127-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-127.us-west-1.compute.internal
      uid: 8f195c51-bcd7-47c5-b091-aa01ecfc729a
    resourceVersion: "17426"
    uid: 45f47313-ad7c-443a-90d6-c618f58edef9
  spec:
    sourcePod: network-check-source-6f78d59f99-n8n9d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:16:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.401328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:16:32Z"
    - latency: 1.363403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 1.825623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 1.073704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 1.010354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 876.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:11:32Z"
    - latency: 1.140558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:10:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:09:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-127-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-127.us-west-1.compute.internal
      uid: 8f195c51-bcd7-47c5-b091-aa01ecfc729a
    resourceVersion: "16583"
    uid: 9b31ebb2-2c63-4ff4-91f6-408a96702b8d
  spec:
    sourcePod: network-check-source-6f78d59f99-n8n9d
    targetEndpoint: aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:15:32Z"
      message: 'load-balancer-api-external: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.292691ms
      message: 'load-balancer-api-external: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 6.89341ms
      message: 'load-balancer-api-external: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 55.565979ms
      message: 'load-balancer-api-external: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 11.742577ms
      message: 'load-balancer-api-external: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 54.99143ms
      message: 'load-balancer-api-external: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 7.966747ms
      message: 'load-balancer-api-external: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 54.552093ms
      message: 'load-balancer-api-external: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 7.849066ms
      message: 'load-balancer-api-external: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 53.372049ms
      message: 'load-balancer-api-external: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:11:32Z"
    - latency: 6.46136ms
      message: 'load-balancer-api-external: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:11:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:09:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-127-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-127.us-west-1.compute.internal
      uid: 8f195c51-bcd7-47c5-b091-aa01ecfc729a
    resourceVersion: "16584"
    uid: 6b098cd6-b984-42b0-a06a-4518b977b98b
  spec:
    sourcePod: network-check-source-6f78d59f99-n8n9d
    targetEndpoint: aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:15:32Z"
      message: 'load-balancer-api-internal: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.31936ms
      message: 'load-balancer-api-internal: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 6.773457ms
      message: 'load-balancer-api-internal: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 55.940428ms
      message: 'load-balancer-api-internal: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 11.704853ms
      message: 'load-balancer-api-internal: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 55.0114ms
      message: 'load-balancer-api-internal: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 7.899677ms
      message: 'load-balancer-api-internal: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 54.670997ms
      message: 'load-balancer-api-internal: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 7.781567ms
      message: 'load-balancer-api-internal: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 53.396789ms
      message: 'load-balancer-api-internal: tcp connection to aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:11:32Z"
    - latency: 6.534388ms
      message: 'load-balancer-api-internal: resolved host name aa122420d47a44699800694ebba22612-7c404a52996dc434.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:11:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:09:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-127-to-network-check-target-ip-10-0-129-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-127.us-west-1.compute.internal
      uid: 8f195c51-bcd7-47c5-b091-aa01ecfc729a
    resourceVersion: "17421"
    uid: 3a8e037f-1c8a-45d1-ba3e-20a61e643755
  spec:
    sourcePod: network-check-source-6f78d59f99-n8n9d
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:16:32Z"
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.787986ms
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:16:32Z"
    - latency: 859.177µs
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 2.196266ms
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 1.458588ms
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 1.067931ms
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 934.278µs
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:11:32Z"
    - latency: 1.897004ms
      message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:10:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:09:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-127-to-network-check-target-ip-10-0-131-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-127.us-west-1.compute.internal
      uid: 8f195c51-bcd7-47c5-b091-aa01ecfc729a
    resourceVersion: "17420"
    uid: b4af081d-255a-4c86-b8fe-a8e299c96f88
  spec:
    sourcePod: network-check-source-6f78d59f99-n8n9d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:16:32Z"
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.013075ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:16:32Z"
    - latency: 2.651041ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 3.393818ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 2.403471ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 1.987495ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 2.044499ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:11:32Z"
    - latency: 2.044092ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:10:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:09:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-127-to-network-check-target-ip-10-0-143-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-127.us-west-1.compute.internal
      uid: 8f195c51-bcd7-47c5-b091-aa01ecfc729a
    resourceVersion: "17422"
    uid: 1291fbbf-a7ab-4c66-9196-31702185bd04
  spec:
    sourcePod: network-check-source-6f78d59f99-n8n9d
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:16:32Z"
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.213994ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:16:32Z"
    - latency: 1.702384ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 2.042913ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 1.668648ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 1.897935ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 1.712708ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:11:32Z"
    - latency: 1.971697ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:10:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T18:09:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-127-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-127.us-west-1.compute.internal
      uid: 8f195c51-bcd7-47c5-b091-aa01ecfc729a
    resourceVersion: "16580"
    uid: 836c4e0d-5b77-408e-b85d-526239fa682f
  spec:
    sourcePod: network-check-source-6f78d59f99-n8n9d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:15:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.443µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 1.720641ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:15:32Z"
    - latency: 1.622455ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 1.798077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:14:32Z"
    - latency: 806.744µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 2.217413ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:13:32Z"
    - latency: 845.307µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 1.747835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:12:32Z"
    - latency: 894.948µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:11:32Z"
    - latency: 1.902588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:11:32Z"
kind: List
metadata:
  resourceVersion: ""