2주만에 출근해서 그런가 집중이 하나도 안되네
먼가 정리해야 할것 같아서 이것저것 하려는데 더 안되고
또 다른 일정으로 인해서(나 없는 2주간 먼가 많이 달라진듯?)
일이 또 달라져서 하던거 또 멈추고 다른거 하게 생겼네..
| 부가세 계산법 (0) | 2019.07.24 |
|---|---|
| 면접 두명 (2) | 2019.07.23 |
| 병원 투어 (0) | 2019.07.19 |
| 스케일링 2차..? (0) | 2019.07.13 |
| 치과.. 아프지 않네? (6) | 2019.07.08 |
아이고 힘들어 ㅠㅠ
| 삐딱구리 딸래미들 (2) | 2019.08.04 |
|---|---|
| 요즘 시국에 롯데마트를 가는것도 웃기긴 한데 (2) | 2019.08.03 |
| 잠에서 헤어나질 못함.. (0) | 2019.07.20 |
| 체력 완전 오링 (0) | 2019.06.30 |
| 밥솥 고장 =_= (0) | 2019.06.27 |
피곤하긴 피곤했나 보다..
몇번이고 기절하듯 잠들고..
| 요즘 시국에 롯데마트를 가는것도 웃기긴 한데 (2) | 2019.08.03 |
|---|---|
| 딸래미와 포켓몬 고 시작 (0) | 2019.07.21 |
| 체력 완전 오링 (0) | 2019.06.30 |
| 밥솥 고장 =_= (0) | 2019.06.27 |
| 그늘막 사서 한강에서 놀기 (2) | 2019.06.23 |
아내님의 긴급 호출로
월차내고 바로 모시러 다녀와서는
씐나는(?) 병원투어
| 면접 두명 (2) | 2019.07.23 |
|---|---|
| 집중력 제로 (2) | 2019.07.22 |
| 스케일링 2차..? (0) | 2019.07.13 |
| 치과.. 아프지 않네? (6) | 2019.07.08 |
| 회사 서버 메모리 이전 (0) | 2019.07.04 |
| # mount overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/XORFE2EOTZ7Q6ZTTXSO25INCEK:/var/lib/docker/overlay2/l/AX5KGBCDRDSLPJXFJN5BEMY46M:/var/lib/docker/overlay2/l/AECCETPS3NK2HMRZPDHLMDZNT2:/var/lib/docker/overlay2/l/UVLPSR7AFYECFPFZDSQWVKICWT,upperdir=/var/lib/docker/overlay2/3e1626d3b52f1b725516abac811574b34873c2c740b45c4911aaa173f0a14c4b/diff,workdir=/var/lib/docker/overlay2/3e1626d3b52f1b725516abac811574b34873c2c740b45c4911aaa173f0a14c4b/work) |
[링크 : https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt]
[링크 : https://en.wikipedia.org/wiki/OverlayFS]
[링크 : https://wiki.archlinux.org/index.php/Overlay_filesystem]
[링크 : ]
| sql join 집합별 쿼리(차집합, 교집합 등등) (0) | 2019.10.22 |
|---|---|
| SPICE (0) | 2019.08.23 |
| bbs and oprom (0) | 2019.06.05 |
| CVE CWE CPE CVSS SCAP (0) | 2019.06.04 |
| QUIC - Quick UDP Internet Connections (0) | 2019.05.25 |
|
$ sudo systemctl restart nfs-server $ sudo systemctl status nfs-server Jul 17 06:15:52 minikube exportfs[15642]: exportfs: /nfs-volume does not support NFS export |
| $ mount rootfs on / type rootfs (rw) devtmpfs on /dev type devtmpfs (rw,relatime,size=955872k,nr_inodes=238968,mode=755) sysfs on /sys type sysfs (rw,relatime) proc on /proc type proc (rw,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) /dev/sda1 on /mnt/sda1 type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/boot2docker type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/docker type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/containers type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/log type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/kubelet type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/cni type ext4 (rw,relatime,data=ordered) /dev/sda1 on /data type ext4 (rw,relatime,data=ordered) /dev/sda1 on /tmp/hostpath_pv type ext4 (rw,relatime,data=ordered) /dev/sda1 on /tmp/hostpath-provisioner type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/minikube type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/toolbox type ext4 (rw,relatime,data=ordered) /dev/sda1 on /var/lib/minishift type ext4 (rw,relatime,data=ordered) /c/Users on /c/Users type vboxsf (rw,nodev,relatime) |
| nfs-kernel-server cannot work with a FUSE folder like an encrypted ecryptfs home directory. |
| rootfs is a special tempfs image used in initram, and stays in this instance because you have an encrypted LVM setup. Normally, init would overwrite rootfs with the actual mounted / file system, but Fedora may not have that fixed with your setup. There is no harm in it. |
[링크 : https://serverfault.com/questions/275988/what-is-rootfs]
| nfs version 과 sparse file (0) | 2019.02.22 |
|---|---|
| svc: failed to register lockdv1 RPC service (errno 111) (0) | 2015.02.10 |
| nfs mount 시 옵션들 (0) | 2012.12.11 |
| mount.nfs: access denied by server while mounting (0) | 2012.06.08 |
| showmount (0) | 2012.06.08 |
되는지는 아직 안해봄
게임이거 까지 해볼순 있으려나?
PAYDAY:The Heist
[링크 : https://darktwins13.tistory.com/911]
PAYDAY 2
[링크 : http://naver.me/5R2e7HKN]
| remember me 한글 패치 (0) | 2020.03.10 |
|---|---|
| 메트로 2033 공략 (2) | 2020.01.12 |
| DCS World 해봄 (4) | 2018.04.08 |
| 프렌즈 마블 벨소리 ㅋㅋㅋ (4) | 2018.03.10 |
| bless 10분...? (0) | 2016.01.27 |
조금 시간이 생겼으니 한번 달려볼까?
SSD도 달렸으니 조금 더 이전보다 부드럽겠지?
[링크 : https://oldgamelove.tistory.com/182]
[링크 : https://blog.naver.com/yjynet04/220994996050]
+
2020.01.11
| 메트로 last light 진행중 (0) | 2020.03.05 |
|---|---|
| metro 2033 : last light 공략 (0) | 2020.02.24 |
| 메트로 2033 엔딩 (2) | 2020.02.23 |
| 오늘의 metro 2033 (0) | 2020.02.22 |
| 메트로 2033 한챕터 진행 (0) | 2020.01.24 |
| 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 |
도움말을 보는데 많이 생략된 느낌이라.. 해보긴 좀 귀찮고.. -_-
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]
| 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 |
|
