apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:54:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-55.ec2.internal
      uid: 1d525aaf-923f-422f-9501-e31848e17c61
    resourceVersion: "22643"
    uid: c4534ba2-e307-48b8-bf5e-d51566c28c9d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vbmz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:01:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.17636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:01:59Z"
    - latency: 1.093166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 1.146538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 1.104935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 846.007µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 1.066677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:56:59Z"
    - latency: 1.232071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:55:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:54:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-55.ec2.internal
      uid: 1d525aaf-923f-422f-9501-e31848e17c61
    resourceVersion: "21530"
    uid: 2fc11f0c-b372-47ab-b483-2cc5b4bc6f36
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vbmz
    targetEndpoint: afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:00:59Z"
      message: 'load-balancer-api-external: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.09975ms
      message: 'load-balancer-api-external: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 9.753386ms
      message: 'load-balancer-api-external: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 5.013763ms
      message: 'load-balancer-api-external: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 8.225769ms
      message: 'load-balancer-api-external: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 4.915816ms
      message: 'load-balancer-api-external: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 8.084597ms
      message: 'load-balancer-api-external: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 5.688566ms
      message: 'load-balancer-api-external: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 8.507232ms
      message: 'load-balancer-api-external: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 4.725095ms
      message: 'load-balancer-api-external: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:56:59Z"
    - latency: 8.691442ms
      message: 'load-balancer-api-external: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:54:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-55.ec2.internal
      uid: 1d525aaf-923f-422f-9501-e31848e17c61
    resourceVersion: "21529"
    uid: 706f924f-bb06-469c-89f2-b541e2b7ef40
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vbmz
    targetEndpoint: afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:00:59Z"
      message: 'load-balancer-api-internal: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.106975ms
      message: 'load-balancer-api-internal: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 9.727698ms
      message: 'load-balancer-api-internal: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 4.039073ms
      message: 'load-balancer-api-internal: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 8.249886ms
      message: 'load-balancer-api-internal: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 4.912013ms
      message: 'load-balancer-api-internal: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 8.054048ms
      message: 'load-balancer-api-internal: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 5.680602ms
      message: 'load-balancer-api-internal: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 8.450133ms
      message: 'load-balancer-api-internal: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 4.588218ms
      message: 'load-balancer-api-internal: tcp connection to afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:56:59Z"
    - latency: 8.613271ms
      message: 'load-balancer-api-internal: resolved host name afd65842ffd604d29a6c0b92405d809d-33896f1b32995da3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-55-to-network-check-target-ip-10-0-137-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-55.ec2.internal
      uid: 1d525aaf-923f-422f-9501-e31848e17c61
    resourceVersion: "22641"
    uid: fc438cc4-7778-40b8-b1b4-4db7f590053b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vbmz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:01:59Z"
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.301581ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:01:59Z"
    - latency: 2.360662ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 2.504691ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 2.400006ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 2.515807ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 2.263232ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:56:59Z"
    - latency: 2.411361ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:55:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-55-to-network-check-target-ip-10-0-141-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-55.ec2.internal
      uid: 1d525aaf-923f-422f-9501-e31848e17c61
    resourceVersion: "22642"
    uid: c65cc0aa-3555-4841-bbd0-62c33df96353
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vbmz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:01:59Z"
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.490877ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:01:59Z"
    - latency: 2.341402ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 2.501503ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 2.387824ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 2.162918ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 1.780578ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:56:59Z"
    - latency: 2.353585ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:55:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:54:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-55-to-network-check-target-ip-10-0-141-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-55.ec2.internal
      uid: 1d525aaf-923f-422f-9501-e31848e17c61
    resourceVersion: "22639"
    uid: d6e10522-07ff-4d3e-9e02-16e195b7663d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vbmz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:01:59Z"
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.118µs
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:01:59Z"
    - latency: 998.13µs
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 959.409µs
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 1.289289ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 1.546743ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 864.04µs
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:56:59Z"
    - latency: 1.777651ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:55:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:54:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-55.ec2.internal
      uid: 1d525aaf-923f-422f-9501-e31848e17c61
    resourceVersion: "21528"
    uid: 997cbe21-365a-46d7-bc30-c1f3a1de46a5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8vbmz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:00:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 2.047343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:00:59Z"
    - latency: 854.905µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 2.039154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:59:59Z"
    - latency: 773.56µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 1.658378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:58:59Z"
    - latency: 803.463µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 1.771929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:57:59Z"
    - latency: 918.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:56:59Z"
    - latency: 1.939423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:56:59Z"
kind: List
metadata:
  resourceVersion: ""