web-deploy | Automatic website deployment with GitHub and PHP | Continuous Deployment library

Looks like a URL issue. Did you check the URL you are invoking? As per the documentation in the link you have shared :

"port 443 inside the Webapp container is mapped to the port 32477 on the Kubernetes cluster.

You need to use https://your-minikube-cluster-ip:your-webapp-service-targetport (e.g., https://10.101.114.46:32477) as the API root URL when using the Postman collection."

But as per your logs, I see the port number used is 31599. https://192.168.88.80:31599/auth/v1/login/

Regards, Prince Arora

Checking out only one directory is not possible, but has been requested in the actions/checkout repository before: https://github.com/actions/checkout/issues/483

There's an action to check out specific files, but I haven't tried it and I'm not sure if it does what you want: https://github.com/marketplace/actions/checkout-files

You might want to ask yourself why you're trying to limit the number of files transferred. Is it because you're concerned about traffic? Or because of the input expected in the subsequent action?

If it's the latter, you could also manually "fix" the structure by running some mv and rm commands.

When defining a property, it includes any line breaks into that property.

This:

There are two networking layers, which we could call "inside the cluster" and "outside the cluster". The Pod and the Service each have their own IP address, but these are only inside the cluster. You need the NodePort to forward a request from outside the cluster to inside the cluster.

In a "real" Kubernetes cluster, you'd make a request...

1. ...to http://any-kubernetes-node.example.com:31245/, with a "normal" IP address in the way you'd expect a physical system to have, connecting to the NodePort port, which forwards...
2. ...to http://web-service.default.svc.cluster.local:80/, with a cluster-internal IP address and the service port, which looks at the pods it selects and forwards...
3. ...to http://10.20.30.40:3000/, using the cluster-internal IP address of any of the matching pods and the target port from the service.

The containerPort: in the pod spec isn't strictly required (but if you give it name: http then you can have the service specify targetPort: http without knowing the specific port number). EXPOSE in the Dockerfile means pretty much nothing in this sequence.

This sequence also gives you some flexibility in not needing to know where things are running. Say you have 100 nodes and 3 replicas of your pod; the initial connection can be to any node, and the service will forward to all of the target pods, without you needing to know any of these details from the caller.

(For completeness, a LoadBalancer type service requests that a load balancer be created outside the cluster; for example, an AWS ELB. This forwards to any of the cluster nodes as in step 1 above. If you're not in a cloud environment and the cluster doesn't know how to create the external load balancer automatically, it's the same as NodePort.)

If we reduce this to a local Kubernetes installation (Docker Desktop, minikube, kind) the only real difference is that there's only one node; the underlying infrastructure is still built as though it were a multi-node distributed cluster. How exactly you access a service differs across these installations. In Docker Desktop, from the host system, you can use localhost as the "normal" "external" node IP address in the first step.

Let me answer on all your questions.

0 - There's no need to create pods separately (unless it's something to test), this should be done by creating deployments (or statefulsets, depends on the app and needs) which will create a replicaset which will be responsible for keeping right amount of pods in operational conditions. (you can get familiar with deployments in kubernetes.

1 - Tunnel is used to expose the service from inside of VM where minikube is running to the host machine's network. Works with LoadBalancer service type. Please refer to access applications in minikube.

1.1 - Reason why the application is not accessible on the localhost:NodePort is NodePort is exposed within VM where minikube is running, not on your local machine.

You can find minikube VM's IP by running minikube IP and then curl %GIVEN_IP:NodePort. You should get a response from your app.

2 - targetPort indicates the service with which port connection should be established. Please refer to define the service.

In minikube it may be confusing since it's pointed to the service port, not to the targetPort which is define within the service. I think idea was to indicate on which port service is accessible within the cluster.

3 - As for this question, there are headers presented, you can treat them literally. For instance:

It looks like your pods are managed by web-deployment deployment. You cannot patch such pods directly.

If you run kubectl get pod -n -oyaml, you'll see a block called ownerReferences under the metadata section. This tells you who is the owner/manager of this pod.

In case of a deployment, here is the ownership hierarchy:

Deployment -> ReplicaSet -> Pod

i.e. A deployment creates replicaset and replicaset in turn creates pod.

So, if you want to change anything in the pod Spec, you should make that change in the deployment, not in the replicaset or the pod directly as they will get overwritten.

Patch your deployment either by running and edit the environment field there:

the problem was with github website.
github's action's status turned incident!
i should've checked out github status page.

I successfully fixed it!

The mistake was that, I just mentioned the password in the posgres_deployment.yaml file, but I should also mention the database name and the username, using which the web_deployment.yaml is trying to access this db service.

Now the new postgres_deployment.yaml file, after the correction, looks like this:

MSDEPLOY_RENAME_LOCKED_FILES

As far as I know, this method only supports Azure Web APP service. This option is used to set the Azure App settings(cloud). It does not apply to IIS deployment(on-prem).

##[error]Error Code: ERROR_FILE_IN_USE

To solve this issue, you could try the following methods:

1.You could set the Take App Offline option in IIS Web Deploy task.

Here is a doc about Taking an Application Offline before Publishing

2.You could Stop your website before deploying the app and restart it after deployment.

You could add IIS web app manage task to stop and start the IIS Website.

For example:

Update1:

As ssinfod's comment: stop the application pool could solve this issue.

We can also achieve this in IIS web app manage task