api-server | 📡 API server for api.cdnjs.com | REST library

I would like to know how Kubernates Ingress works.

1. Is there an apply order, service and deployment are applied, does ingress come before or after?
2. To test ingress with azure, I created a kubernates service in azure (service and deployment, etc. applied there). In Azure there is the API-Serveraddress under the Kubernate version or under Network (like xyzzy.123.k8s.io ). Can I enter this domain as a host in my Ingress YAML?

like this:

We have a full-blown setup using AWS EKS with Tekton installed and want to use ArgoCD for application deployment.

As the docs state we installed ArgoCD on EKS in GitHub Actions with:

I have cloned this NEAR REST API SERVER repo into my local system and haven't made any changes to its original code. Only added console logs for debugging purpose. Using its API, I have successfully deployed a contract to testnet account and also called that contract.

But when comes to NFT part, its not working. I'm calling /mint_nft API and getting 500 Internal Server Error.

It's breaking here:

let create_token = await token.ViewNFT(tokenId, contract);

create_token is null.

If I do minting with NEAR CLI, its working fine and I can see that NFT in my testnet wallet..

near call $ID nft_mint '{"token_id": "02", "receiver_id": "'$ID'", "token_metadata": { "title": "Design #2", "description": "Art Design", "media": "https://ipfs.io/ipfs/Qme7ss3ARVgxv6rXqVPiikMJ8u2NLgmgszg13pYrDKEoiu", "copies": 1}}' --accountId $ID --deposit 0.1

I have 2 Elastic Beanstalk environments, "api-server" & "website". Both have a capacity of 1-4 EC2 instances and a load balancer. The load balancer and the instances have both public IP addresses. I want to connect from the "website" to the "api-server" but i can't get it to work without making the "api-server" public. The "api-server" should not be public.

I am connected with a VPN that is allowed HTTP connections to both EB environments and i can confirm that both apps respond.

Both EB environments have 2 security groups, one for the load balancer called "Load Balancer Security Group" and one for the instances called "VPC Security Group". All load balancer and VPC security groups have an outbound rule allowing all traffic on all protocols.

Since i want to connect from the "website" to any of the instances of "api-server" i want to connect to the load balancer and not to any of the instances directly. So i should add an inbound rule to the load balancer group of the "api-server" that allows traffic from the "website"'s instances.

The instances all have the "VPC Security Group" but adding the rule did not give the "website" instances access to the "api-server". I also tried adding the load balancer security group without success. And i also tried the type "All traffic".

I also tried to connect to the "api-server" over different URLs like the load balancer but also no connection possible.

When i add a rule that allows traffic to everywhere, eg. source type "Anywhere-IPv4", i can access the "api-server" from the website. But as i said i don't want the "api-server" public it should be accessible only by the "website".

What also works is adding a rule with the IP address of the current "website" instance, but since they change with deployment of a new version and they are sometimes more or less instances (autoscaled from 1 to 4) its not an option.

So how does it work?

I searched everywhere in the docs but i can't find anything i didn't already tried. What am i missing? This surely shouldn't be so hard?

I appreciate every help!

Edit: Everything is in the same VPC.

I try to get the json-data from a api-server. I can't add this to the variable. I got the error

Type is missing the following properties from Type "Observable" missing the properties from type "GAMELIST[]": "length, pop, push, concat" und 27 weitere.ts(2740)

Where I is my mistake?

I had installed kube-prometheus-stack from the helm chart repo prometheus-community

I am trying to configure a nginx Docker container to serve the Angular application on its root path (which works so far) and make the backend via a proxy on /api available.

I've read multiple threads on Stackoverflow and some blogs, but no configuration worked so far. If I call my app on / the Angular app works. When I try to call /api on the same url it gets redirected to / and shows no content -- I guess the Angular router got some route it cannot handle. But Nginx should catch that route before the Angular app gets called. How do I do that?

I am not sure what is wrong. Do you see the error in my config?

I'm writing a Lambda function using Axios to make calls to my external API server. My goal is to perform two steps:

Step one is to authenticate my user to retrieve an access token. Step two is to use that access token in order to GET server alarms.

The first part axios.post works and the access token shows in the logs. I cannot seem to set that as a variable to pass to the second step. If I have it as two separate functions it does not know what the token value is, so I was trying to potentially nest the axios functions to see if that could read the value. I now receive a TypeError: (intermediate value)}.then is not a function.

Here's where I stand with the the Lambda function. I appreciate the help!

I created a NodeJS application which should get some data from an external API-Server. That server provides its data only as 'Content-Type: text/plain;charset=ISO-8859-1'. I have got that information through the Header-Data of the server.

Now the problem for me is that special characters like 'ä', 'ö' or 'ü' are shown as �. I tried to convert them with Iconv to UTF-8, but then I got these things '�'...

My question is, what am I doing wrong?

For testing I use Postman. These are the steps I do to test everything:

• Use Postman to trigger my NodeJS application
• The App requests data from the API-Server
• API-Server sends Data to NodeJS App
• My App prints out the raw response-data of the API, which already has those strange characters �
• The App then tries to convert them with Iconv to UTF-8, where it shows me now this '�' characters

Another strange thing: When I connect Postman directly to the API-Server, the special characters get shown as they have too without problems. Therefore i guess my application causes the problem but I cannot see where or why...

// Javascript Code: