apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-148-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-148.ec2.internal
      uid: fcc606cc-5004-400b-ba5e-be5ce03b8d52
    resourceVersion: "14612"
    uid: 7ad5f0b8-3e67-49c1-930b-588cf2bc85bc
  spec:
    sourcePod: network-check-source-869dcfcdcd-8q9mq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:47:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.76µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:27Z"
    - latency: 1.024902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 908.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 964.474µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 1.052349ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 897.628µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:42:27Z"
    - latency: 1.007556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-148-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-148.ec2.internal
      uid: fcc606cc-5004-400b-ba5e-be5ce03b8d52
    resourceVersion: "14162"
    uid: 587c1167-7e37-4cbc-b7ef-0ba2e89e7189
  spec:
    sourcePod: network-check-source-869dcfcdcd-8q9mq
    targetEndpoint: a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:46:27Z"
      message: 'load-balancer-api-external: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.329818ms
      message: 'load-balancer-api-external: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 8.619427ms
      message: 'load-balancer-api-external: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 5.686026ms
      message: 'load-balancer-api-external: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 8.336593ms
      message: 'load-balancer-api-external: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 5.969023ms
      message: 'load-balancer-api-external: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 7.916068ms
      message: 'load-balancer-api-external: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 6.838881ms
      message: 'load-balancer-api-external: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 9.153869ms
      message: 'load-balancer-api-external: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 4.120207ms
      message: 'load-balancer-api-external: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:42:27Z"
    - latency: 8.311882ms
      message: 'load-balancer-api-external: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-148-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-148.ec2.internal
      uid: fcc606cc-5004-400b-ba5e-be5ce03b8d52
    resourceVersion: "14161"
    uid: ce1f68ff-ba07-426d-b92b-bee9ae824dc8
  spec:
    sourcePod: network-check-source-869dcfcdcd-8q9mq
    targetEndpoint: a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:46:27Z"
      message: 'load-balancer-api-internal: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.323133ms
      message: 'load-balancer-api-internal: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 8.510896ms
      message: 'load-balancer-api-internal: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 5.686433ms
      message: 'load-balancer-api-internal: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 8.365173ms
      message: 'load-balancer-api-internal: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 5.976672ms
      message: 'load-balancer-api-internal: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 7.847725ms
      message: 'load-balancer-api-internal: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 4.030436ms
      message: 'load-balancer-api-internal: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 9.180164ms
      message: 'load-balancer-api-internal: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 4.129675ms
      message: 'load-balancer-api-internal: tcp connection to a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:42:27Z"
    - latency: 8.210607ms
      message: 'load-balancer-api-internal: resolved host name a37b41d7c50ea4581a30197ec6bd3bcf-4dd5307222ea3acb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-148-to-network-check-target-ip-10-0-130-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-148.ec2.internal
      uid: fcc606cc-5004-400b-ba5e-be5ce03b8d52
    resourceVersion: "14609"
    uid: 43d2c922-3f03-43db-a691-6fc93ef04d57
  spec:
    sourcePod: network-check-source-869dcfcdcd-8q9mq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:47:27Z"
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.066476ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:27Z"
    - latency: 2.409534ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 2.160353ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 2.788632ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 2.279306ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 2.314687ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:42:27Z"
    - latency: 2.33817ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-148-to-network-check-target-ip-10-0-136-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-148.ec2.internal
      uid: fcc606cc-5004-400b-ba5e-be5ce03b8d52
    resourceVersion: "14610"
    uid: e117e93f-2520-4449-9701-fd69149c3f20
  spec:
    sourcePod: network-check-source-869dcfcdcd-8q9mq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:47:27Z"
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.324µs
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:27Z"
    - latency: 930.45µs
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 1.390962ms
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 872.988µs
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 1.031255ms
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 1.362718ms
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:42:27Z"
    - latency: 1.614718ms
      message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-148-to-network-check-target-ip-10-0-143-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-148.ec2.internal
      uid: fcc606cc-5004-400b-ba5e-be5ce03b8d52
    resourceVersion: "14611"
    uid: 952d8f45-e1d8-4446-bb4c-d088d8d28df4
  spec:
    sourcePod: network-check-source-869dcfcdcd-8q9mq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:47:27Z"
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.273836ms
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:27Z"
    - latency: 2.12321ms
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 2.11885ms
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 2.255745ms
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 2.455839ms
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 2.069202ms
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:42:27Z"
    - latency: 2.158691ms
      message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-148-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-148.ec2.internal
      uid: fcc606cc-5004-400b-ba5e-be5ce03b8d52
    resourceVersion: "14160"
    uid: 4d30423b-2227-4520-aed7-36263090bc19
  spec:
    sourcePod: network-check-source-869dcfcdcd-8q9mq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:46:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 942.097µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 2.038165ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:46:27Z"
    - latency: 829.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 2.11632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:45:27Z"
    - latency: 906.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 1.893409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:44:27Z"
    - latency: 946.716µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 1.744036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:43:27Z"
    - latency: 858.426µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:42:27Z"
    - latency: 1.644856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:42:27Z"
kind: List
metadata:
  resourceVersion: ""