Unable to setup development environment for Kiali - istio

I want to setup developer environment for Kiali-ui. I am following Kiali guide to do this.
But while accessing Kiali on browser(http://localhost:3000) i am getting following issue:
Not Found
Cannot GET /api/auth/info
From console logs I am getting following issue:
Failed to load resource: the server responded with a status of 404 (Not Found)
I am using this link to setup proxy for the API requests:
"name": "#kiali/kiali-ui",
"version": "1.49.0",
"proxy": "http://{IP-OF-KIALI}:20001"
Is there any pre-requisite to setup development environment for Kiali-ui?

I was giving wrong url of Kiali in package.json.
Following url works for me:
"proxy": "http://{IP-OF-KIALI}:20001/kiali"
This url is of Kiali which running inside k8s pod.

Related

Enabling auth mode sso("Login Via google") after install argocd 2.4.3

Recently we migrated from 2.3.3 to 2.4.3 and we are using google sso with argocd by script https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.3/manifests/install.yaml .
It used to show "Login Via google" In 2.3.3 with out any additional settings but now its showing only uid/pwd boxes.
we are already injecting argocd-cm
dex.config: |
connectors:
- config:
issuer: https://accounts.google.com
clientID: {{ .Values.dex.sso.clientId }}
clientSecret: $dex.sso.clientSecret
type: oidc
id: google
name: Google
I googled and got to know that setting auth-mode to sso might enable "login-via-google" login button
argo server --auth-mode sso --auth-mode ...
We tried to change the auth-mode to sso but I could not find a way to set the auth-mode in https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.3/manifests/install.yaml or via env variable in argocd-cm
Please help me in this regards
Regards,
Shubhendu

deploy nuxtjs application to GCP, but it gives server error?

I'm new to GCP (google cloud platform) I'm facing this problem, Backend dev created an Apache server on gcp, and then I cloned my repo on the server through VM, build it and then deployed it after following countless tutorials.. but while deploying it gives
Cloud Run error: Container failed to start. Failed to start and then listen on the port defined by the PORT environment variable.
when i go to the generated link which is https://vetution.oa.r.appspot.com/ it gives server error, I've searched a lot but I failed.
Have I done something wrong or the app.yaml file should have different configurations.
anyway here it is
runtime: nodejs12
instance_class: F2
handlers:
- url: /_nuxt
static_dir: .nuxt/dist/client
secure: always
- url: /(.*\.(gif|png|jpg|ico|txt))$
static_files: static/\1
upload: static/.*\.(gif|png|jpg|ico|txt)$
secure: always
- url: /.*
script: auto
secure: always
env_variables:
HOST: '0.0.0.0'
NODE_ENV: 'production'
And It gives me this error on deploying now
please, Help me I'm very frustrated.
The error states that, your app failed to start because it's not listening to a port as you may not have configure it to your app. This topic is answered on this Stackoverflow thread.
You mentioned that you followed countless tutorials, it is possible that you are using Cloud Run and App Engine interchangeably, which are 2 separate serverless products. Please evaluate on your end which platform is right for your app and use case.
Currently, there is not much debugging info to your question but either way, make sure that you configure your app's port to listen to incoming request/s, it can be port 8080 or can be any of your choice. Also, check your GCP logs, backend issues and server errors can be seen and monitored by simply looking at the logs for App Engine or Cloud Run.
Check Cloud Run configuring the container ports, for port configuration.

react app fails when deployed to GitHub-pages but works fine on local host

https://github.com/naftalib/news-feed
Get a blank page, dev tools gives this error on multiple resources;
Failed to load resource: the server responded with a status of 404 (Not Found)
In the end the problem was that the .gitattributes file was mistakenly deleted from the public folder when cleaning up files.

Why does kompose up yields "connection refused"?

Running docker-compose up on a simple web app works as expected. Running kompose up on the same app while attempting to connect to a Google Cloud cluster doesn't work:
...
INFO We are going to create Kubernetes Deployments, Services and PersistentVolumeClaims for your Dockerized application. If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead.
FATA Error while deploying application: Get http://127.0.0.1:6443/api: dial tcp 127.0.0.1:6443: connect: connection refused
What are possible causes of this problem?
Other posts here on SO do not help, and I can't find any other relevant result on the web.

Angular8: Call localhost Rest Api services

I developed my web application with Angular 8. The backend is a rest api that I developed with django rest framework and it's viewed just in the localhost. I tested it and it works fine. For example the service http://127.0.0.1:8000/api/devices gives a list of devices. It gives a good results if I test it with browser or curl command.
I'm calling this service from my angular app. I executed the angular app with the command: ng serve --host 0.0.0.0 --port 4201
If I open the web application in the browser with http://127.0.0.1:4201/api/devices the service /api/devices is well called and I get the list of devices in my web page. but if I open the web application with my LAN IP address like that http://192.168.1.59:4201/api/devices, so I get HTTP 400 bad request error in my console.
And the same error is shown in django server traces: GET /api/devices/ HTTP/1.1" 400 26
After some searches in the internet I concluded that this error is frequently coming from angular app especially the proxy:
my proxy config file proxy.config.json is:
{
"/api" : {
"target": "http://localhost:8000",
"secure": false
}
}
I mad other searches and I found an answer to similar question Angular 6 call localhost API and after following the angular doc https://angular.io/guide/build in "Proxying to a backend server" section then I modified my proxy config file to:
{
"/api": {
"target": "http://localhost:8000",
"secure": false,
"pathRewrite": {
"^/api": ""
}
}
}
Has any one an idea what can be the main cause of the issue? and how I can fix it?
ng serve --host 0.0.0.0 --port 4201 --disable-host-check