Compare commits

..

No commits in common. "2b3edfba190076a9517722b1ab9f38ee7cf7e4f1" and "e7fb506118fa3d842d1bdfe8839dd5fce711313c" have entirely different histories.

6 changed files with 0 additions and 127 deletions

View File

@ -1,27 +0,0 @@
alloy:
resources: {} # resource 설정 가능
configMap:
create: true
content: |-
// 여기서부터 컴포넌트 코드 작성
// Alloy 에서는 //, /* */를 주석으로 사용합니다.
discovery.kubernetes "kube_system_pods" {
role = "pod"
namespaces {
names = ["kube-system"]
}
}
loki.source.kubernetes "kube_system_pods" {
targets = discovery.kubernetes.kube_system_pods.targets
forward_to = [loki.write.loki_instance.receiver]
}
loki.write "loki_instance" {
endpoint {
url = "<LOKI_ENDPOINT>"
}
}

View File

@ -1,29 +0,0 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: alloy-config
data:
config.alloy: |-
// 여기서부터 컴포넌트 코드 작성
// Alloy 에서는 //, /* */를 주석으로 사용합니다.
discovery.kubernetes "kube_system_pods" {
role = "pod"
namespaces {
names = ["kube-system"]
}
}
loki.source.kubernetes "kube_system_pods" {
targets = discovery.kubernetes.kube_system_pods.targets
forward_to = [loki.write.loki_instance.receiver]
}
loki.write "loki_instance" {
endpoint {
url = "<LOKI_ENDPOINT>"
}
}

View File

@ -1,8 +0,0 @@
alloy:
resources: {} # resource 설정 가능
configMap:
create: false
name: alloy-config
key: config.alloy

View File

@ -1,31 +0,0 @@
#!/bin/bash
ALLOY_CONFIG_PATH="<ALLOY_FILE_PATH>"
NAMESPACE="<NAMESPACE>"
CM_NAME="<CONFIGMAP_NAME>"
ALLOY_POD_NAME=$(kubectl get pod -l app.kubernetes.io/name=alloy -n $NAMESPACE -o jsonpath='{.items[*].metadata.name}')
RED="\033[31m"
GREEN="\033[32m"
YELLOW="\033[33m"
RESET="\033[0m"
echo -e "${RED}[1/3] Applying configmap file: $ALLOY_CONFIG_PATH on namespace=$NAMESPACE${RESET}"
if kubectl create configmap $CM_NAME --from-file=$ALLOY_CONFIG_PATH --dry-run=client -o yaml | kubectl apply -f - -n $NAMESPACE; then
echo -e "${GREEN}[1/3] Configmap applied successfully.${RESET}"
else
echo -e "${RED}[1/3] Failed to apply configmap.${RESET}"
exit 1
fi
echo -e "${YELLOW}[2/3] Waiting 1 second...${RESET}"
sleep 1
echo -e "${RED}[3/3] Triggering reload on pod=$ALLOY_POD_NAME...${RESET}"
if kubectl exec -it "$ALLOY_POD_NAME" -n "$NAMESPACE" -c config-reloader -- wget --post-data="" -O /dev/null http://localhost:12345/-/reload; then
echo -e "${GREEN}[3/3] Reload triggered successfully.${RESET}"
else
echo -e "${RED}[3/3] Failed to trigger reload.${RESET}"
exit 1
fi

View File

@ -1,23 +0,0 @@
// Alloy 에서는 //, /* */를 주석으로 사용합니다.
discovery.kubernetes "kube_system_pods" {
role = "pod"
namespaces {
names = ["kube-system"]
}
}
loki.source.kubernetes "kube_system_pods" {
targets = discovery.kubernetes.kube_system_pods.targets
forward_to =
}
loki.write "loki_intance" {
endpoint {
url = "<YOUR_LOKI_ENDPOINT>"
}
}
discovery.kubernetes "name" {
}

View File

@ -1,9 +0,0 @@
# v2와 helm 설정은 동일함.
alloy:
resources: {} # resource 설정 가능
configMap:
create: false
name: alloy-config
key: config.alloy