'프로그램 사용'에 해당되는 글 2263건

  1. 2019.07.16 kubernetes selector
  2. 2019.07.16 kubernetes delete pods with namespace
  3. 2019.07.16 kubernetes ImagePullBackOff 에러
  4. 2019.07.16 yaml
  5. 2019.07.16 kubectl
  6. 2019.07.15 Dockerfile... 2?
  7. 2019.07.15 우분투에 쿠버네티스 설치하기(minikube 사용없이)
  8. 2019.07.15 win10에서 hyper-v 끄기
  9. 2019.07.15 docker remote
  10. 2019.07.15 virtualbox headless

'프로그램 사용 > kubernetes' 카테고리의 다른 글

rancher  (0) 2020.10.06
kubernetes delete pods with namespace  (0) 2019.07.16
kubernetes ImagePullBackOff 에러  (0) 2019.07.16
yaml  (0) 2019.07.16
kubectl  (0) 2019.07.16
Posted by 구차니

도움말을 보는데 많이 생략된 느낌이라.. 해보긴 좀 귀찮고.. -_-

namespace를 지우면 거기 들어있는 pods도 같이 삭제된다.

 

>kubectl help delete pod
Delete resources by filenames, stdin, resources and names, or by resources and label selector.

 JSON and YAML formats are accepted. Only one type of the arguments may be specified: filenames, resources and names, or
resources and label selector.

 Some resources, such as pods, support graceful deletion. These resources define a default period before they are
forcibly terminated (the grace period) but you may override that value with the --grace-period flag, or pass --now to
set a grace-period of 1. Because these resources often represent entities in the cluster, deletion may not be
acknowledged immediately. If the node hosting a pod is down or cannot reach the API server, termination may take
significantly longer than the grace period. To force delete a resource, you must pass a grace period of 0 and specify
the --force flag.

 IMPORTANT: Force deleting pods does not wait for confirmation that the pod's processes have been terminated, which can
leave those processes running until the node detects the deletion and completes graceful deletion. If your processes use
shared storage or talk to a remote API and depend on the name of the pod to identify themselves, force deleting those
pods may result in multiple processes running on different machines using the same identification which may lead to data
corruption or inconsistency. Only force delete pods when you are sure the pod is terminated, or if your application can
tolerate multiple copies of the same pod running at once. Also, if you force delete pods the scheduler may place new
pods on those nodes before the node has released those resources and causing those pods to be evicted immediately.

 Note that the delete command does NOT do resource version checks, so if someone submits an update to a resource right
when you submit a delete, their update will be lost along with the rest of the resource.

Examples:
  # Delete a pod using the type and name specified in pod.json.
  kubectl delete -f ./pod.json

  # Delete resources from a directory containing kustomization.yaml - e.g. dir/kustomization.yaml.
  kubectl delete -k dir

  # Delete a pod based on the type and name in the JSON passed into stdin.
  cat pod.json | kubectl delete -f -

  # Delete pods and services with same names "baz" and "foo"
  kubectl delete pod,service baz foo

  # Delete pods and services with label name=myLabel.
  kubectl delete pods,services -l name=myLabel

  # Delete a pod with minimal delay
  kubectl delete pod foo --now

  # Force delete a pod on a dead node
  kubectl delete pod foo --grace-period=0 --force

  # Delete all pods
  kubectl delete pods --all

Options:
      --all=false: Delete all resources, including uninitialized ones, in the namespace of the specified resource types.
  -A, --all-namespaces=false: If present, list the requested object(s) across all namespaces. Namespace in current
context is ignored even if specified with --namespace.
      --cascade=true: If true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a
ReplicationController).  Default true.
      --field-selector='': Selector (field query) to filter on, supports '=', '==', and '!='.(e.g. --field-selector
key1=value1,key2=value2). The server only supports a limited number of field queries per type.
  -f, --filename=[]: containing the resource to delete.
      --force=false: Only used when grace-period=0. If true, immediately remove resources from API and bypass graceful
deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires
confirmation.
      --grace-period=-1: Period of time in seconds given to the resource to terminate gracefully. Ignored if negative.
Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion).
      --ignore-not-found=false: Treat "resource not found" as a successful delete. Defaults to "true" when --all is
specified.
  -k, --kustomize='': Process a kustomization directory. This flag can't be used together with -f or -R.
      --now=false: If true, resources are signaled for immediate shutdown (same as --grace-period=1).
  -o, --output='': Output mode. Use "-o name" for shorter output (resource/name).
  -R, --recursive=false: Process the directory used in -f, --filename recursively. Useful when you want to manage
related manifests organized within the same directory.
  -l, --selector='': Selector (label query) to filter on, not including uninitialized ones.
      --timeout=0s: The length of time to wait before giving up on a delete, zero means determine a timeout from the
size of the object
      --wait=true: If true, wait for resources to be gone before returning. This waits for finalizers.

Usage:
  kubectl delete ([-f FILENAME] | [-k DIRECTORY] | TYPE [(NAME | -l label | --all)]) [options]

Use "kubectl options" for a list of global command-line options (applies to all commands).

 

아무튼 찾아보니 --namespce 옵션에 값을 주어 특정 ns상의 pods를 삭제할 수 있어 보인다.

kubectl delete --all pods --namespace=foo
kubectl delete --all namespaces

[링크 : https://stackoverflow.com/questions/33509194/command-to-delete-all-pods-in-all-kubernetes-namespaces]

'프로그램 사용 > kubernetes' 카테고리의 다른 글

rancher  (0) 2020.10.06
kubernetes selector  (0) 2019.07.16
kubernetes ImagePullBackOff 에러  (0) 2019.07.16
yaml  (0) 2019.07.16
kubectl  (0) 2019.07.16
Posted by 구차니

git으로 로컬에 저장해두고 push 안한 상태에서

pull 하려고 하면 발생하는 에러

(본인이 직접 container 생성하는게 아니라면 볼일이 없을 듯)

 

[링크 : https://managedkube.com/.../imagepullbackoff/2019/02/23/imagepullbackoff.html]

'프로그램 사용 > kubernetes' 카테고리의 다른 글

kubernetes selector  (0) 2019.07.16
kubernetes delete pods with namespace  (0) 2019.07.16
yaml  (0) 2019.07.16
kubectl  (0) 2019.07.16
우분투에 쿠버네티스 설치하기(minikube 사용없이)  (0) 2019.07.15
Posted by 구차니

저...언혀 사람이 쓰기 안편한데...

내가 사람이 아닌건가?!

(아니 난.. XML이나 JSON이 훨 편한데? ㅠㅠ)

 

[링크 : https://yaml.org/]

 

+

헐.. JSON의 슈퍼셋이 YAML이라니.. YAML이 더 큰거였다니!?!

Technically YAML is a superset of JSON. This means that, in theory at least, a YAML parser can understand JSON, but not necessarily the other way around.

See the official specs, in the section entitled "YAML: Relation to JSON".

[링크 : https://stackoverflow.com/questions/1726802/]

 

+

어짜피 그게 그거라 docker에서도 json으로 쓰면 yml이랑 상관없이 알아서 읽는 듯?

[링크 : https://docs.docker.com/compose/faq/]

Posted by 구차니

docker 처럼 명령어가 넘쳐나는구만

 

C:>kubectl
kubectl controls the Kubernetes cluster manager.

 Find more information at: https://kubernetes.io/docs/reference/kubectl/overview/

Basic Commands (Beginner):
  create         Create a resource from a file or from stdin.
  expose         Take a replication controller, service, deployment or pod and expose it as a new
Kubernetes Service
  run            Run a particular image on the cluster
  set            Set specific features on objects

Basic Commands (Intermediate):
  explain        Documentation of resources
  get            Display one or many resources
  edit           Edit a resource on the server
  delete         Delete resources by filenames, stdin, resources and names, or by resources and
label selector

Deploy Commands:
  rollout        Manage the rollout of a resource
  scale          Set a new size for a Deployment, ReplicaSet, Replication Controller, or Job
  autoscale      Auto-scale a Deployment, ReplicaSet, or ReplicationController

Cluster Management Commands:
  certificate    Modify certificate resources.
  cluster-info   Display cluster info
  top            Display Resource (CPU/Memory/Storage) usage.
  cordon         Mark node as unschedulable
  uncordon       Mark node as schedulable
  drain          Drain node in preparation for maintenance
  taint          Update the taints on one or more nodes

Troubleshooting and Debugging Commands:
  describe       Show details of a specific resource or group of resources
  logs           Print the logs for a container in a pod
  attach         Attach to a running container
  exec           Execute a command in a container
  port-forward   Forward one or more local ports to a pod
  proxy          Run a proxy to the Kubernetes API server
  cp             Copy files and directories to and from containers.
  auth           Inspect authorization

Advanced Commands:
  diff           Diff live version against would-be applied version
  apply          Apply a configuration to a resource by filename or stdin
  patch          Update field(s) of a resource using strategic merge patch
  replace        Replace a resource by filename or stdin
  wait           Experimental: Wait for a specific condition on one or many resources.
  convert        Convert config files between different API versions
  kustomize      Build a kustomization target from a directory or a remote url.

Settings Commands:
  label          Update the labels on a resource
  annotate       Update the annotations on a resource
  completion     Output shell completion code for the specified shell (bash or zsh)

Other Commands:
  api-resources  Print the supported API resources on the server
  api-versions   Print the supported API versions on the server, in the form of "group/version"
  config         Modify kubeconfig files
  plugin         Provides utilities for interacting with plugins.
  version        Print the client and server version information

Usage:
  kubectl [flags] [options]

Use "kubectl <command> --help" for more information about a given command.
Use "kubectl options" for a list of global command-line options (applies to all commands).

'프로그램 사용 > kubernetes' 카테고리의 다른 글

kubernetes ImagePullBackOff 에러  (0) 2019.07.16
yaml  (0) 2019.07.16
우분투에 쿠버네티스 설치하기(minikube 사용없이)  (0) 2019.07.15
win10에서 hyper-v 끄기  (0) 2019.07.15
minikube  (0) 2019.07.15
Posted by 구차니
프로그램 사용/docker2019. 7. 15. 15:51

 

Dockerfile

COPY .(host) .(container)

CMD 는 ENTRYPOINT의 일부(둘다 지정시)


CMD
The CMD instruction has three forms:
CMD ["executable","param1","param2"] (exec form, this is the preferred form)
CMD ["param1","param2"] (as default parameters to ENTRYPOINT)
CMD command param1 param2 (shell form) <<<<< SHELL FORM

 


docker run -it ubuntu bash
는 cmd를 엎어 씀
entrypoint는 덮어 쓸수 없음(그렇기에 entry point없이 cmd만으로 된것으로 확인할수 있음)

        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "/bin/bash"
            ],
            "ArgsEscaped": true,
            "Image": "sha256:ae950a0376fe6c4d08fa7ff395f50f4a909e26e9f2d865d8641cda024161c6ee",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": null
        },

----

docker run help
      --entrypoint string              Overwrite the default ENTRYPOINT of the image

 


[링크 : https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact]

 

 

복수개의 Run

FROM golang:1.11-alpine AS build

# Install tools required for project
# Run `docker build --no-cache .` to update dependencies
RUN apk add --no-cache git
RUN go get github.com/golang/dep/cmd/dep

# List project dependencies with Gopkg.toml and Gopkg.lock
# These layers are only re-built when Gopkg files are updated
COPY Gopkg.lock Gopkg.toml /go/src/project/
WORKDIR /go/src/project/
# Install library dependencies
RUN dep ensure -vendor-only

# Copy the entire project and build it
# This layer is rebuilt when a file changes in the project directory
COPY . /go/src/project/
RUN go build -o /bin/project

# This results in a single layer image
FROM scratch
COPY --from=build /bin/project /bin/project
ENTRYPOINT ["/bin/project"]
CMD ["--help"]


[링크 : https://docs.docker.com/develop/develop-images/dockerfile_best-practices/]

'프로그램 사용 > docker' 카테고리의 다른 글

도커 cpu 갯수 제한  (0) 2024.03.22
docker snap 버전 문제  (0) 2022.10.12
docker remote  (0) 2019.07.15
UTS name space  (0) 2019.07.15
LXC LXD  (0) 2019.07.15
Posted by 구차니

'프로그램 사용 > kubernetes' 카테고리의 다른 글

kubernetes ImagePullBackOff 에러  (0) 2019.07.16
yaml  (0) 2019.07.16
kubectl  (0) 2019.07.16
win10에서 hyper-v 끄기  (0) 2019.07.15
minikube  (0) 2019.07.15
Posted by 구차니

'프로그램 사용 > kubernetes' 카테고리의 다른 글

kubernetes ImagePullBackOff 에러  (0) 2019.07.16
yaml  (0) 2019.07.16
kubectl  (0) 2019.07.16
우분투에 쿠버네티스 설치하기(minikube 사용없이)  (0) 2019.07.15
minikube  (0) 2019.07.15
Posted by 구차니
프로그램 사용/docker2019. 7. 15. 15:48

docker의 환경변수로 특정 서버를 지정해줄때 아래와 같이

DOCKER_HOST 변수를 통해 기본으로 사용될 원격 서버를 변경할 수 있다.

 

minikube docker-env | Invoke-Expression


SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://192.168.99.100:2376
SET DOCKER_CERT_PATH=C:\Users\CCCR-EDU-5\.minikube\certs
REM Run this command to configure your shell:
REM @FOR /f "tokens=*" %i IN ('minikube docker-env') DO @%i

[링크 : https://stackoverflow.com/questions/44446472/docker-run-on-a-remote-host]

'프로그램 사용 > docker' 카테고리의 다른 글

docker snap 버전 문제  (0) 2022.10.12
Dockerfile... 2?  (0) 2019.07.15
UTS name space  (0) 2019.07.15
LXC LXD  (0) 2019.07.15
docker ps exited만 보기  (0) 2019.07.10
Posted by 구차니

virtualbox headless 옵션은 background로 실행한다.

[링크 : https://twpower.github.io/149-run-virutalbox-vm-in-background]

Posted by 구차니