Closed vadiml77 closed 2 years ago
Hi @vadiml77, could you please send us the manifest for the headless service? You can send it to BridgeToKubernetes@microsoft.com, or attach it here. Thanks!
Hi, sorry, the service is being load balanced. Here is the yaml for the service. I've XXX out few fields.
apiVersion: v1 kind: Pod metadata: creationTimestamp: "2022-02-13T22:03:27Z" generateName: ssp-dev-ssp-factor-6fb9687f46- labels: app: ssp-factor app.kubernetes.io/component: webservice app.kubernetes.io/instance: ssp-dev app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: ssp-factor app.kubernetes.io/part-of: ssp app.kubernetes.io/version: 1.0.2666 helm.sh/chart: ssp-1.0.2666 pod-template-hash: 6fb9687f46 managedFields:
Hi @vadiml77, sorry for the slow reply. I've produced a new CLI build that contains some extra logging as well as a tiny code change. Can you please follow the instructions here and let us know the results? https://github.com/microsoft/mindaro/issues/288#issuecomment-1055588516
OK, was able to get further with the latest plugin (v1.0.120220125) in OSX VSCode
The issue with this NPE appears to be presence of endpoints having no target IP Address. Not sure if that was limited to a specific namespace or all namespaces. Do "kubectl get endpoints" and make sure there ate no endpoints without a target ip address
Once we removed services that were also creating an endpoint without a target IP address, I was able to get past this issue. It looks like Bridge, while reading endpoint data, should also take care of the possiblity there will be no target data
Thanks so much for trying again and letting us know, and glad you found a workaround. I'll document this bug on our side
Describe the bug I'm getting the following error with Briudge to Kubernetes - "Error: Failed to validate the requirements to replicate resources locally: An unexpected error occurred: 'Object reference not set to an instance of an object.'" The service is a headless service fronted by an ingress exposing https URL forwarding to service port on 443.
Any help / ideas will be greatly appreciated.
To Reproduce Steps to follow to reproduce this issue.
**Expected behavior** A clear and concise description of what you expected to happen. **Logs** Attach logs from the following directory: For Windows: %TEMP%/Bridge to Kubernetes For OSX/Linux: $TMPDIR/Bridge to Kubernetes If you are a Visual Studio user, - Set the environment variable MS_VS_AZUREDEVSPACES_TOOLS_LOGGING_ENABLED=true - Open Visual Studio and run your scenario - Provide logs from: %temp%\Microsoft.VisualStudio.Kubernetes.Debugging **bridge-library-2022-02-13-22-46-11-9900.txt** 2022-02-13T22:46:11.3586650Z | Library | TRACE | Pulling kubeconfig...\nOperation context: