apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-98-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-98.ec2.internal
      uid: 3ea6879d-af11-4823-bec9-33775205f41d
    resourceVersion: "14842"
    uid: f405351f-d6ad-467f-aafb-5247a00ac37f
  spec:
    sourcePod: network-check-source-7d88cb55d8-7vjfx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.154µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:58Z"
    - latency: 1.296968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:58Z"
    - latency: 934.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:58Z"
    - latency: 786.403µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:58Z"
    - latency: 1.024611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:58Z"
    - latency: 1.205511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:58Z"
    - latency: 1.103103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-98-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-98.ec2.internal
      uid: 3ea6879d-af11-4823-bec9-33775205f41d
    resourceVersion: "16577"
    uid: 65b7868f-21a5-4bd1-8ad8-6626ef3823e0
  spec:
    sourcePod: network-check-source-7d88cb55d8-7vjfx
    targetEndpoint: a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:56:58Z"
      message: 'load-balancer-api-external: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.222223ms
      message: 'load-balancer-api-external: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:58Z"
    - latency: 12.524702ms
      message: 'load-balancer-api-external: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:02:58Z"
    - latency: 4.699964ms
      message: 'load-balancer-api-external: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:58Z"
    - latency: 10.635065ms
      message: 'load-balancer-api-external: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:01:58Z"
    - latency: 5.392541ms
      message: 'load-balancer-api-external: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:58Z"
    - latency: 8.721323ms
      message: 'load-balancer-api-external: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:58Z"
    - latency: 4.941504ms
      message: 'load-balancer-api-external: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:58Z"
    - latency: 7.660488ms
      message: 'load-balancer-api-external: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:58Z"
    - latency: 6.103542ms
      message: 'load-balancer-api-external: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:58Z"
    - latency: 7.238922ms
      message: 'load-balancer-api-external: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-98-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-98.ec2.internal
      uid: 3ea6879d-af11-4823-bec9-33775205f41d
    resourceVersion: "16576"
    uid: 3c14b016-4251-4901-8357-11de7f496a23
  spec:
    sourcePod: network-check-source-7d88cb55d8-7vjfx
    targetEndpoint: a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:56:58Z"
      message: 'load-balancer-api-internal: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.204524ms
      message: 'load-balancer-api-internal: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:58Z"
    - latency: 12.615203ms
      message: 'load-balancer-api-internal: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:02:58Z"
    - latency: 4.758122ms
      message: 'load-balancer-api-internal: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:58Z"
    - latency: 10.702042ms
      message: 'load-balancer-api-internal: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:01:58Z"
    - latency: 5.376732ms
      message: 'load-balancer-api-internal: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:58Z"
    - latency: 8.766679ms
      message: 'load-balancer-api-internal: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:58Z"
    - latency: 4.866579ms
      message: 'load-balancer-api-internal: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:58Z"
    - latency: 7.718428ms
      message: 'load-balancer-api-internal: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:58Z"
    - latency: 6.121527ms
      message: 'load-balancer-api-internal: tcp connection to a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:58Z"
    - latency: 7.2776ms
      message: 'load-balancer-api-internal: resolved host name a834cf6563d064043b4f6f8b241975d3-6db6eb84bb15c813.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-98-to-network-check-target-ip-10-0-133-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-98.ec2.internal
      uid: 3ea6879d-af11-4823-bec9-33775205f41d
    resourceVersion: "14841"
    uid: 2adaece1-3c55-4a01-9a3a-262593d2f79f
  spec:
    sourcePod: network-check-source-7d88cb55d8-7vjfx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:58Z"
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.412828ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:58Z"
    - latency: 2.147012ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:58Z"
    - latency: 2.416354ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:58Z"
    - latency: 2.306845ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:58Z"
    - latency: 2.192136ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:58Z"
    - latency: 2.247216ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:58Z"
    - latency: 2.732263ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-98-to-network-check-target-ip-10-0-139-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-98.ec2.internal
      uid: 3ea6879d-af11-4823-bec9-33775205f41d
    resourceVersion: "14839"
    uid: 7f000a5c-0a1f-4b3f-b3ed-68c7d80665d9
  spec:
    sourcePod: network-check-source-7d88cb55d8-7vjfx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:58Z"
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.767µs
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:58Z"
    - latency: 1.522974ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:58Z"
    - latency: 932.945µs
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:58Z"
    - latency: 1.32748ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:58Z"
    - latency: 1.041797ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:58Z"
    - latency: 1.21843ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:58Z"
    - latency: 1.416627ms
      message: 'network-check-target-ip-10-0-139-98: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-98-to-network-check-target-ip-10-0-142-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-98.ec2.internal
      uid: 3ea6879d-af11-4823-bec9-33775205f41d
    resourceVersion: "14840"
    uid: 6aaf4233-6def-4939-a011-b6d814ea4c2d
  spec:
    sourcePod: network-check-source-7d88cb55d8-7vjfx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:58Z"
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.3014ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:58Z"
    - latency: 2.453003ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:58Z"
    - latency: 2.25339ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:58Z"
    - latency: 2.391935ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:58Z"
    - latency: 2.207953ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:58Z"
    - latency: 2.517844ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:58Z"
    - latency: 2.472611ms
      message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-98-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-98.ec2.internal
      uid: 3ea6879d-af11-4823-bec9-33775205f41d
    resourceVersion: "16575"
    uid: 9522f391-5014-44e7-8e8b-fd93b6746d18
  spec:
    sourcePod: network-check-source-7d88cb55d8-7vjfx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:56:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:58Z"
    - latency: 1.566296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:02:58Z"
    - latency: 1.176588ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:58Z"
    - latency: 1.762153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:01:58Z"
    - latency: 766.232µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:58Z"
    - latency: 1.691133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:58Z"
    - latency: 902.158µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:58Z"
    - latency: 1.94822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:58Z"
    - latency: 1.474426ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:58Z"
    - latency: 1.704319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:58Z"
kind: List
metadata:
  resourceVersion: ""