apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-142.ec2.internal
      uid: fe5a96df-ac01-432c-904c-6db947e20280
    resourceVersion: "23643"
    uid: 0001691c-b683-40d9-a60f-e189faa874f9
  spec:
    sourcePod: network-check-source-685456655f-2v4lf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:00:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.147168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:13Z"
    - latency: 1.201956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 938.195µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 1.143771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 1.14393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 1.074225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:55:13Z"
    - latency: 1.141698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:54:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-142.ec2.internal
      uid: fe5a96df-ac01-432c-904c-6db947e20280
    resourceVersion: "22194"
    uid: da7ff0e0-b9d8-4b67-b042-708eaa01e597
  spec:
    sourcePod: network-check-source-685456655f-2v4lf
    targetEndpoint: a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:59:13Z"
      message: 'load-balancer-api-external: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.338134ms
      message: 'load-balancer-api-external: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 6.553152ms
      message: 'load-balancer-api-external: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 4.478506ms
      message: 'load-balancer-api-external: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 6.771889ms
      message: 'load-balancer-api-external: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 5.281361ms
      message: 'load-balancer-api-external: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 6.132071ms
      message: 'load-balancer-api-external: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 5.699784ms
      message: 'load-balancer-api-external: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 6.531619ms
      message: 'load-balancer-api-external: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 5.387949ms
      message: 'load-balancer-api-external: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:55:13Z"
    - latency: 6.879831ms
      message: 'load-balancer-api-external: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-142.ec2.internal
      uid: fe5a96df-ac01-432c-904c-6db947e20280
    resourceVersion: "22195"
    uid: 4dfc4e32-1d5e-4e47-9dd1-a07164b72f57
  spec:
    sourcePod: network-check-source-685456655f-2v4lf
    targetEndpoint: a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:59:13Z"
      message: 'load-balancer-api-internal: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.294486ms
      message: 'load-balancer-api-internal: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 6.614303ms
      message: 'load-balancer-api-internal: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 4.002474ms
      message: 'load-balancer-api-internal: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 6.793988ms
      message: 'load-balancer-api-internal: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 5.350502ms
      message: 'load-balancer-api-internal: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 6.08114ms
      message: 'load-balancer-api-internal: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 5.996496ms
      message: 'load-balancer-api-internal: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 6.407825ms
      message: 'load-balancer-api-internal: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 5.373211ms
      message: 'load-balancer-api-internal: tcp connection to a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:55:13Z"
    - latency: 6.83968ms
      message: 'load-balancer-api-internal: resolved host name a8f792013ccdf4e68ab0f39b50b3190d-43d053cbdd92676e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-142-to-network-check-target-ip-10-0-129-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-142.ec2.internal
      uid: fe5a96df-ac01-432c-904c-6db947e20280
    resourceVersion: "23640"
    uid: d54e161e-73be-4be1-aedf-7fb5c1b6f4d0
  spec:
    sourcePod: network-check-source-685456655f-2v4lf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:00:13Z"
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.792889ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:13Z"
    - latency: 984.466µs
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 961.96µs
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 946.038µs
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 1.413203ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 1.070579ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:55:13Z"
    - latency: 1.318884ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:54:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-142-to-network-check-target-ip-10-0-131-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-142.ec2.internal
      uid: fe5a96df-ac01-432c-904c-6db947e20280
    resourceVersion: "23642"
    uid: 2456a1cd-0b47-4e8e-8b29-33cea2c81049
  spec:
    sourcePod: network-check-source-685456655f-2v4lf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:00:13Z"
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.348023ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:13Z"
    - latency: 1.950332ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 2.182951ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 2.122379ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 2.297965ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 1.913973ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:55:13Z"
    - latency: 2.137476ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:54:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-142-to-network-check-target-ip-10-0-138-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-142.ec2.internal
      uid: fe5a96df-ac01-432c-904c-6db947e20280
    resourceVersion: "23641"
    uid: c24bab99-03f3-4e3c-aebd-47bb95d14aea
  spec:
    sourcePod: network-check-source-685456655f-2v4lf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:00:13Z"
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.15183ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:13Z"
    - latency: 2.2898ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 2.047371ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 2.006037ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 1.973486ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 1.972956ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:55:13Z"
    - latency: 2.018431ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:54:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:53:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-142.ec2.internal
      uid: fe5a96df-ac01-432c-904c-6db947e20280
    resourceVersion: "22193"
    uid: e85d7d60-1862-478a-b745-6b3cb29dec7a
  spec:
    sourcePod: network-check-source-685456655f-2v4lf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:59:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 1.789103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:59:13Z"
    - latency: 1.029878ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 1.9209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:58:13Z"
    - latency: 1.015156ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 1.714169ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:57:13Z"
    - latency: 1.289249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 1.758311ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:56:13Z"
    - latency: 778.057µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:55:13Z"
    - latency: 1.946937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:55:13Z"
kind: List
metadata:
  resourceVersion: ""